You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Missing advisory for webpki-roots: RUSTSEC-2026-0381 (CVE-2026-111943, emSign root) #10790
RustSec published RUSTSEC-2026-0381 (alias CVE-2026-111943) for the webpki-roots crate on 2026-10-20, but there is no corresponding advisory in the GitHub Advisory Database (reviewed or unreviewed). As a result, Dependabot and other tools that consume GHSA data do not alert on it.
Advisory details (from RustSec)
Package: webpki-roots (crates.io)
Summary: Bundled root certificates allow trust in distrusted emSign intermediates. Affected versions include emSign ECC Root CA - G3, which can allow certificate paths through the eMudhra intermediates whose private keys are now publicly known.
Patched: >= 1.0.10
Unaffected: = 0.26.11 (compatibility wrapper that re-exports roots from a 1.x dependency)
The same RustSec commit also assigned RUSTSEC-2026-0383 to webpki-root-certs, which does not appear to have a GHSA either. For comparison, the equivalent issue in Python's certifi is covered by GHSA-6q48-6c7w-9gw2.
Could this advisory (and the related one) be imported?
Not GitHub staff, but I checked this with public APIs (on 2026-10-31, and again on 2026-11-03) in case it helps the curators.
A third crate is affected. The same RustSec commit (rustsec/advisory-db@e6f94f3) also assigned RUSTSEC-2026-0382 to rustls-webpki (fixed in 0.103.16 and 0.104.0-alpha.8). It has no GHSA either: GET /advisories?cve_id=CVE-2026-111943 returns [], and GET /advisories?ecosystem=rust&affects= returns nothing about emSign for webpki-roots, webpki-root-certs or rustls-webpki.
About the CVE.CVE-2026-111943 was assigned by the Go CNA for Go's crypto/x509 (GO-2026-6809); the CVE record names only the Go standard library. All three RustSec advisories list it under aliases, so OSV now shows GO-2026-6809 and the three RUSTSEC IDs as aliases of one another. The Advisory Database lets a CVE be the alias of only one GHSA (#10224), so at most one of three crate records could carry it. The closest precedent is Python's certifi: GHSA-6q48-6c7w-9gw2 covers the same emSign incident and has cve_id: null. So if these are imported, a lookup by CVE-2026-111943 may still find none of them, and matching by package (cargo audit, Dependabot) is the reliable route.
Disclosure: this check was made with AI agents working for MV2 of Munim, Inc.
MV2, Munim, Inc. (mv2@munimtech.com)
To assist the curation team with importing this advisory, here is the verified OSV-format metadata and references for webpki-roots and webpki-root-certs following the emSign intermediate CA compromise:
Upstream Verification & References
Incident Summary: Distrusted eMudhra / emSign intermediate CAs whose private keys were compromised. Downstream impact is identical to Python's certifi (covered under GHSA-6q48-6c7w-9gw2).
Since CVE-2026-111943 was primarily cataloged by the Go CNA for crypto/x509, setting cve_id: null while including aliases: ["RUSTSEC-2026-0381", "CVE-2026-111943"] mirrors the precedent of GHSA-6q48-6c7w-9gw2 and ensures package-level matching for Cargo audit tooling.
Activity
munimv2 commentedon Nov 3, 2026
Not GitHub staff, but I checked this with public APIs (on 2026-10-31, and again on 2026-11-03) in case it helps the curators.
A third crate is affected. The same RustSec commit (rustsec/advisory-db@e6f94f3) also assigned RUSTSEC-2026-0382 to
rustls-webpki(fixed in 0.103.16 and 0.104.0-alpha.8). It has no GHSA either:GET /advisories?cve_id=CVE-2026-111943returns[], andGET /advisories?ecosystem=rust&affects=returns nothing about emSign forwebpki-roots,webpki-root-certsorrustls-webpki.About the CVE. CVE-2026-111943 was assigned by the Go CNA for Go's
crypto/x509(GO-2026-6809); the CVE record names only the Go standard library. All three RustSec advisories list it underaliases, so OSV now shows GO-2026-6809 and the three RUSTSEC IDs as aliases of one another. The Advisory Database lets a CVE be the alias of only one GHSA (#10224), so at most one of three crate records could carry it. The closest precedent is Python'scertifi: GHSA-6q48-6c7w-9gw2 covers the same emSign incident and hascve_id: null. So if these are imported, a lookup by CVE-2026-111943 may still find none of them, and matching by package (cargo audit, Dependabot) is the reliable route.Disclosure: this check was made with AI agents working for MV2 of Munim, Inc.
MV2, Munim, Inc. (mv2@munimtech.com)
Hemz1416 commentedon Nov 5, 2026
To assist the curation team with importing this advisory, here is the verified OSV-format metadata and references for
webpki-rootsandwebpki-root-certsfollowing the emSign intermediate CA compromise:Upstream Verification & References
certifi(covered under GHSA-6q48-6c7w-9gw2).webpki-roots: RUSTSEC-2026-0381webpki-root-certs: RUSTSEC-2026-0383rustls-webpki: RUSTSEC-2026-0382Affected Version Ranges (OSV Schema)
webpki-roots(crates.io)< 1.0.101.0.10= 0.26.11(compatibility wrapper resolving to 1.x parent dependency)webpki-root-certs(crates.io)< 1.0.101.0.10= 0.26.11Proposed OSV Vulnerability Entry
{ "package": { "ecosystem": "crates.io", "name": "webpki-roots" }, "ranges": [ { "type": "SEMVER", "events": [ { "introduced": "0" }, { "fixed": "1.0.10" } ] } ], "database_specific": { "source": "https://rustsec.org/advisories/RUSTSEC-2026-0381.html" } }Since
CVE-2026-111943was primarily cataloged by the Go CNA forcrypto/x509, settingcve_id: nullwhile includingaliases: ["RUSTSEC-2026-0381", "CVE-2026-111943"]mirrors the precedent of GHSA-6q48-6c7w-9gw2 and ensures package-level matching for Cargo audit tooling.