CVE-2019-9634: DLL Injection on Windows in Go stdlib
Summary
CVE-2019-9634: DLL injection on Windows in runtime and syscall. Affects stdlib across 2 version ranges.
< 1.11.10
>= 1.12.0-0, < 1.12.2
Fixed in 1.11.10 or 1.12.2, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Go stdlib package is a collection of standard libraries that provide fundamental functionality for Go programs. It includes various modules for tasks such as file handling, networking, and system operations. The vulnerability in question affects the Go stdlib package on Windows operating systems. It specifically involves the misuse of certain LoadLibrary functionality, which can result in DLL injection.
Vulnerability Detail
The vulnerability arises from the incorrect usage of LoadLibrary functionality in Go on Windows. This can allow an attacker to inject malicious DLLs into the runtime or system calls, potentially leading to unauthorized code execution or privilege escalation. The issue can have severe consequences, compromising the integrity and security of the affected system.
How To Fix
Latest published version: go1.25.5 as of 22 Oct 2026
go get stdlib@vgo1.25.5Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 1.11.101.11.10go get stdlib@v1.11.10 -
>= 1.12.0-0, < 1.12.21.12.2go get stdlib@v1.12.2
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a workaround, developers can manually modify the affected code to ensure proper usage of LoadLibrary functionality. This may involve reviewing and updating code that interacts with the runtime or system calls on Windows. It is crucial to follow secure coding practices and validate inputs to prevent potential DLL injection attacks.
Conclusion
The DLL injection vulnerability in the Go stdlib package on Windows can have significant security implications. It is crucial for developers to update to the fixed version and follow secure coding practices to mitigate the risk of DLL injection attacks. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for stdlib →
FAQ
DLL injection is a technique used by attackers to insert malicious code into a running process by forcing it to load a dynamic-link library (DLL). This can be exploited to gain unauthorized access, execute arbitrary code, or escalate privileges.
This vulnerability impacts Windows systems running Go programs that use the affected versions of the Go stdlib package. It can allow attackers to inject malicious DLLs, potentially leading to unauthorized code execution or privilege escalation.
No, not all versions are affected. The vulnerability was introduced in version 1.12.0-0 and was fixed in version 1.12.2. It is recommended to update to the fixed version to mitigate the risk.
The consequences of this vulnerability can be severe. Attackers can exploit DLL injection to execute arbitrary code within the context of a vulnerable process, potentially compromising the system's integrity, confidentiality, and availability.
At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is essential to address the issue promptly by updating the Go stdlib package to the fixed version.
References
Related vulnerabilities
Recent vulnerabilities recorded for stdlib.
