Go vulnerabilitiesAnd the versions its exploited flaws hit.
Go is made by Golang. We track 124 published vulnerabilities in it, across 245 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 10 October 2023. If you run Go, check your version against the exploited flaws below and patch those first.
The most recent Go flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.
Which versions of Go do the exploited flaws hit?
Each exploited flaw lists the versions it affects, usually as ranges. "1.12 to before 1.12.16" means from 1.12 up to, but not including, 1.12.16. Find your version, then patch.
- CVE-2020-0601Exploited list, 3 Nov 2021
Microsoft Windows CryptoAPI Spoofing Vulnerability
1.12 to before 1.12.161.13 to before 1.13.7
1 more exploited flaw names Go without a version of its own, for example as the system other affected software runs on. It is in the list below.
Which Go vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.5HTTP/2 Rapid Reset Attack Vulnerability
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
- 8.1Microsoft Windows CryptoAPI Spoofing Vulnerability
Microsoft Windows CryptoAPI (Crypt32.dll) contains a spoofing vulnerability in the way it validates Elliptic Curve Cryptography (ECC) certificates.
Which Go flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
- 89%
A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates.An attacker could exploit the vulnerability by using a spoofed code-signing...
- 66%CVE-2018-16873High
In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go package, or a package that imports it...
- 63%CVE-2018-7187High
The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only checks for "://" anywhere in the string), which allows remote attackers to...
- 11%CVE-2021-38297Critical
Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH=wasm GOOS=js is used.
- 10.0%CVE-2022-24675High
encoding/pem in Go before 1.17.9 and 1.18.x before 1.18.1 has a Decode stack overflow via a large amount of PEM data.
- 9.6%CVE-2015-5739Critical
The net/http library in net/textproto/reader.go in Go before 1.4.3 does not properly parse HTTP header keys, which allows remote attackers to conduct HTTP request smuggling attacks via a space instead of a hyphen, as...
- 9.3%CVE-2017-15041Critical
Go before 1.8.4 and 1.9.x before 1.9.1 allows "go get" remote command execution.
- 8.4%CVE-2019-14809Critical
net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some applications.
- 7.6%CVE-2018-6574High
Go before 1.8.7, Go 1.9.x before 1.9.4, and Go 1.10 pre-releases before Go 1.10rc2 allow "go get" remote command execution during source code build, by leveraging the gcc or clang plugin feature, because -fplugin=...
Running Go? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).
- Matched to
- Go on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 124 published vulnerabilities listed under the name Go, across 245 versions. The most recent Go flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2023-44487 and CVE-2020-0601.
Each flaw names its own versions, usually as ranges. The newest, CVE-2020-0601, affects 1.12 to before 1.12.16, 1.13 to before 1.13.7. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Go. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.