CVE-2026-32281: Go standard library crypto/x509 · Inefficient Algorithmic Complexity
Affects Go standard library crypto/x509Source CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 1.26.2 or 1.25.9 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.26.2, 1.25.9
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade Go standard library crypto/x509 to 1.26.2 or 1.25.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Go standard librarycrypto/x509 | Affected
| Fixed in
|
| Go standard librarycrypto/x509 | Affected
| Fixed in
|
Gocrypto/x509pkg:golang/crypto/x509Other threats | Affected
| Fixed in
|
Gogithub.com/golang/go/src/crypto/x509pkg:golang/github.com/golang/go/src/crypto/x509Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, users should be aware of the potential for denial of service when validating certificate chains with numerous policy mappings. No vendor advisory or patch links are currently available, so no official mitigation steps can be recommended beyond monitoring for updates from the Go project.
Description
Validating certificate chains which use policies is unexpectedly inefficient when certificates in the chain contain a very large number of policy mappings, possibly causing denial of service. This only affects validation of otherwise trusted certificate chains, issued by a root CA in the VerifyOptions.Roots CertPool, or in the system certificate pool.