Bundled root certificates allow trust in distrusted emSign intermediates
Products / packages Go standard library crypto/x509 · webpki-roots · rustls-webpki · 2 more
Published
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NSeverity
medium6.8CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Not established by this record
Missing evidence does not mean no public exploit exists.
Remediation
Package fixes recorded
Fix versions are recorded for 4 of 4 mapped packages. Check each release branch and any separate product guidance.
What this means
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.
Source excerpt · OSVAttack conditions
No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
Go standard library · Go
crypto/x509
2 ranges
Go standard library · Go
crypto/x509
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 1.26.10
semver versions
1.27.0-0 → before 1.27.3
semver versions
Other versions: unaffected
Packages
Compare each installed version with the publisher’s affected ranges. Where a fix is recorded, choose the appropriate release branch and test compatibility before upgrading.
| Affected range | Recorded fix |
|---|---|
| From 0.0.0-0 before 0.26.11Semantic versions | 0.26.11 |
| From 0.26.12-0 before 1.0.10Semantic versions | 1.0.10 |
Version evidence: OSV · RUSTSEC-2026-0381
View original version evidence (0 explicit versions)
| Affected range | Recorded fix |
|---|---|
| From 0.0.0-0 before 0.103.16Semantic versions | 0.103.16 |
| From 0.104.0-alpha.1 before 0.104.0-alpha.8Semantic versions | 0.104.0-alpha.8 |
Version evidence: OSV · RUSTSEC-2026-0382
View original version evidence (0 explicit versions)
| Affected range | Recorded fix |
|---|---|
| From 0.0.0-0 before 0.26.11Semantic versions | 0.26.11 |
| From 0.26.12-0 before 1.0.10Semantic versions | 1.0.10 |
Version evidence: OSV · RUSTSEC-2026-0383
View original version evidence (0 explicit versions)
| Affected range | Recorded fix |
|---|---|
| Earlier releases before 1.26.10Semantic versions | 1.26.10 |
| From 1.27.0-0 before 1.27.3Semantic versions | 1.27.3 |
Version evidence: OSV · GO-2026-6809
View original version evidence (0 explicit versions)
What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
Use the recorded fix for your release branch. Review the publisher’s instructions and test compatibility before upgrading.
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.
Original source description
Read the full publisher description
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.
References
15 sourcesView 9 more references
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-111943View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 3
Assigning organization
Additional data publisher
Additional data publisher
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Source updated
Latest modification date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.