Skip to content
Log inStart free trial

RUSTSEC-2026-0382 BIT-golang-2026-111943 CVE-2026-111943 GO-2026-6809 RUSTSEC-2026-0381 RUSTSEC-2026-0383

Certificate verification may accept distrusted intermediates

Medium Gocrates.io
Severity
6.8 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.40%
Chance of exploitation in the next 30 days. Higher than 33.80% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-299 Improper Check for Certificate Revocation
Fix
Available
4 packages have a fixed version

Description

Affected versions may accept certificate paths containing distrusted emSign intermediate public keys when the configured trust anchors allow such paths. The private keys corresponding to these intermediates are now well known.

Versions 0.103.16 and 0.104.0-alpha.8 reject paths containing these public keys.

Affected versions

Go

PackageVulnerableFixed in
stdlib
< 1.26.10
>= 1.27.0-0, < 1.27.3
1.26.10
1.27.3

crates.io

PackageVulnerableFixed in
rustls-webpki
>= 0.0.0-0, < 0.103.16
>= 0.104.0-alpha.1, < 0.104.0-alpha.8
0.103.16
0.104.0-alpha.8
webpki-root-certs
>= 0.0.0-0, < 0.26.11
>= 0.26.12-0, < 1.0.10
0.26.11
1.0.10
webpki-roots
>= 0.0.0-0, < 0.26.11
>= 0.26.12-0, < 1.0.10
0.26.11
1.0.10

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

stdlib Go → 1.27.3

go
go get stdlib@v1.27.3 && go mod tidy

rustls-webpki crates.io → 0.104.0-alpha.8

cargo
cargo update -p rustls-webpki --precise 0.104.0-alpha.8

webpki-root-certs crates.io → 1.0.10

cargo
cargo update -p webpki-root-certs --precise 1.0.10

webpki-roots crates.io → 1.0.10

cargo
cargo update -p webpki-roots --precise 1.0.10

Severity breakdown

CVSS 3.1 6.8

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Weakness

CWE-299: Improper Check for Certificate Revocation

The product does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised.

How to prevent it
  • Architecture and Design: Ensure that certificates are checked for revoked status.
  • Implementation: If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the revoked status.

References

Advisories

Fixes and patches

Issue reports

Packages

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-4374-p667-p6c8
HTTP/2 rapid reset can cause excessive work in net/http
High Known exploited Also affects stdlib
CVE-2020-0601
Certificate validation bypass on Windows in crypto/x509
High Known exploited Also affects stdlib
GO-2026-6613
HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http
High Also affects stdlib
GO-2026-6609
Lack of limit on size of parsed Range headers in net/http
High Also affects stdlib
GO-2026-6608
Memory limit bypass when parsing MIME headers in net/textproto, mime/multipart
High Also affects stdlib
GO-2026-6607
Reject malformed ECH outer extension references in crypto/tls
High Also affects stdlib
GO-2026-6604
Root.Mkdir(All) can follow junctions out of the root on Windows in os
Critical Also affects stdlib
GO-2026-6600
Recognize yield as regexp preceder keyword in html/template
Medium Also affects stdlib
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor