The short version
- The compromise. The private keys of eight eMudhra intermediate CA certificates were compromised, and anyone holding one could issue a certificate for any website a browser would accept. A researcher reported it to the root programmes on the evening of 17 October, and Chrome and Firefox blocked the certificates within hours.
- Why the keys were weak. According to Mozilla's incident report, all eight were P-384 private keys generated in April 2025 with values smaller than 256, so anyone could recover them by testing 256 numbers. eMudhra blamed a script error that produced a second set of weaker keys.
- No evidence of misuse. eMudhra says most of the affected intermediates were never used in production and that it found no evidence they were used to issue certificates to end users. The keys could have been recovered and abused since April 2025, though there is no evidence that happened.
- Patching is uneven. Browsers blocked the certificates automatically, but Go, Python certifi, NSS and other bundles needed their own releases, and some fixes work by removing a root entirely, cutting off legitimate certificates too. Node.js fixes are still pending.
Timeline
| Date | Event |
|---|---|
| April 2025 | eMudhra generates the eight intermediate certificates with the weak P-384 keys, which it later attributes to a script error. |
| 17 Oct | A researcher credited as Wayne reports the compromise to the root programmes; Chrome blocks the six TLS intermediates by 19:45 UTC and Mozilla finishes its OneCRL push at 22:59 UTC. |
| 19 Oct | Apple blocks the certificates. |
| 20 Oct | Microsoft blocks them, Mozilla removes emSign ECC Root CA - G3 from NSS, and Firefox 158.0.1 and Go 1.27.3 and 1.26.10 ship with fixes. |
How the keys were compromised
A researcher credited by Mozilla only as Wayne reported the compromised keys to the root programmes at 18:05 UTC on 17 October, according to the Chrome Root Program. Mozilla's Dennis Jackson wrote that Wayne signed a message with each of the eight keys. Chrome had a blocking CRLSet update in place by 19:45 UTC and Mozilla finished pushing its OneCRL block at 22:59 UTC; both are revocation lists that browsers fetch themselves, so no update or restart was needed.
According to Mozilla's incident report, all eight used P-384 private keys generated in April 2025 with values smaller than 256, so anyone could recover them by testing 256 possible numbers. eMudhra told Mozilla that a script error produced a second, weaker set of keys that was picked for signing because the labels resembled the properly generated ones. Researcher Flüpke published one key on GitHub with a value of 4; BleepingComputer said it verified that the key matched a revoked certificate.
Who was exposed
The eight are six TLS intermediates — domain, organisation and extended validation — and two for code signing. Chrome blocked only the six TLS ones, because its verifier will not build a path through an intermediate restricted to code signing. No TLS certificate chaining to the six had been logged to Certificate Transparency, a public log of issued certificates, before the block, so none could have been trusted by default in browsers that require logging, Chrome's root programme said.
Apple blocked the certificates on 19 October and Microsoft on 20 October, according to Jackson's tracking site. Each of the eight also exists as a copy cross-signed by Sectigo under its AAA Certificate Services root, but that did not widen the risk in Chrome or Firefox: both stopped trusting that root for websites in April 2025. Apple's root list for iOS 26 and macOS 26 does include it.
eMudhra has revoked all eight and stopped issuing certificates under its G3 root. It told Mozilla that most of the affected intermediates were never used in production and that it found no evidence they were used to issue certificates to end users.
The patching picture
Go 1.27.3 and 1.26.10, released on 20 October, reject any chain containing one of the eight keys on Go's own verifier and on the macOS and Windows system-verifier paths, with no setting to turn it off. A program picks this up only when it is rebuilt, and Go 1.25 and older are out of support. Firefox 158.0.1 and its ESR updates cover installations that cannot receive Remote Settings; NSS 3.131.1, Python certifi 2026.10.19 and Rust webpki-roots 1.0.10 are also out.
Three of those fixes remove roots rather than block the keys. certifi, webpki-roots and Homebrew's ca-certificates drop emSign ECC Root CA - G3, and Homebrew also excludes emSign Root TLS CA - G3 and AAA Certificate Services. Mozilla, which removed emSign ECC Root CA - G3 from NSS on 20 October, said some servers will become unavailable to non-Firefox users of its trust list until they move to new certificate chains.
Some updates are still outstanding. Both accounts list Node.js as pending; they disagree on Composer's ca-bundle, which one lists as pending and the other as released in versions 1.4.16 and 1.6.0. Jackson warned that macOS's built-in curl may keep trusting the compromised certificates, because its bundle does not check revocation information.
What is not known yet
- Whether anyone other than the researcher held or used the keys at any point between April 2025 and the block on 17 October.
- How the weak keys left eMudhra's control and when.
- Whether any end-user certificate was ever issued under the affected intermediates.
- What further action Chrome takes against eMudhra's roots, beyond blocking the eight certificates.
- When the pending Node.js fix will ship.
What to do
If you run Go services or ship software with its own trust store
- Rebuild affected binaries with Go 1.27.3; Go 1.25 and older receive no fix.
- Update any bundled certificate store to the fixed release named in the tracking advisory, such as Python certifi 2026.10.19.
- Check macOS's /usr/bin/curl separately, because its bundle does not check revocation.
If you operate a trust store or non-browser TLS clients
- Test whether your systems still accept the certificates, using the test endpoints published with the advisory.
- Block the eight intermediates where your software can block individual intermediates.
- Where clients cannot check revocation and refuse connections when they cannot, consider removing trust in emSign ECC Root CA - G3, and expect legitimate certificates chaining to it to fail until servers move to new chains.
For everyone else
- Install available browser, NSS and language-bundle updates; Firefox with Remote Settings enabled needs nothing further.
- Do not treat a certificate as trustworthy on a client that cannot check revocation and refuses connections when it cannot.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.