CVE-2026-111943
mediumOn most platforms, Go uses the given system root certificates.
On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.
CVSS
6.8
6.8 (CVSS v3.1)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Severity source: NVD CVSS v3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
Timeline (UTC)
Published: 2026-10-21 01:17
Modified: 2026-10-30 13:18
NVD status: Awaiting Analysis
Last synced 1 day ago
Verified against the source API 2026-11-03 07:34 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).
Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://go.dev/cl/851047 security@golang.org
- https://go.dev/issue/82345 security@golang.org
- https://groups.google.com/g/golang-announce/c/66pojueaQek security@golang.org
- https://pkg.go.dev/vuln/GO-2026-6809 security@golang.org
- http://www.openwall.com/lists/oss-security/2026/10/20/29 af854a3a-2127-422b-91ae-364da2661108
Data sources
NVD CVE API 2.0 — fetched 2026-11-03 07:34 UTC · record ↗