eMudhra CA Private Keys Compromised
The private keys of eight eMudhra intermediate certificate authority certificates have been compromised. Mozilla and Google confirmed the breach on October 20, 2026, after a researcher reported it on the evening of October 17. The eMudhra CA compromise lets anyone holding these keys issue trusted TLS certificates for any website. This article breaks down what happened, who is affected, and what defenders should do next.
What Happened: eMudhra CA Private Keys Exposed in Global TLS Trust Crisis
eMudhra is an Indian certificate authority that sells certificates under the emSign brand. It holds roots in the Mozilla, Chrome, Apple, and Microsoft trust stores. The compromised keys belong to eight intermediate CA certificates used for TLS and code signing.
A researcher named Wayne reported the compromise on October 17 by signing the message “We have a problem here – Wayne” with each of the eight private keys. Chrome and Firefox blocked the certificates within hours. eMudhra revoked the certificates. Apple blocked them on October 19, and Microsoft followed on October 20.
Technical Details of the eMudhra Certificate Authority Compromise
The eight compromised certificates covered domain-validated, organization-validated, and extended-validation TLS. They also included two code-signing intermediates. The six TLS certificates chain to emSign ECC Root CA – G3, which Mozilla removed from its trust store on October 20.
Each certificate also exists as a cross-signed copy under Sectigo’s AAA Certificate Services root. However, Chrome and Firefox stopped trusting that root for websites in April 2025, which limited the extra risk from the cross-signed copies.
How the Weak Keys Made Exploitation Trivial
The compromised private keys were catastrophically weak. A normal NIST P-384 private key holds roughly 384 bits of entropy. The compromised keys ranged from 3 to 8 bits. The actual private key values were only 4, 56, 66, 115, 155, 156, 230, and 237. Such small values mean an attacker could derive the private key in seconds.
Anyone with the private key can issue a certificate that browsers will trust by default. The attack requires an adversary-in-the-middle position, which is well within reach of nation-states, ISPs, and attackers on local networks.
Business and Operational Impact
The impact is global because the certificates are trusted by default in major browsers and operating systems. Organizations and users face the following risks:
- Man-in-the-middle attacks against any TLS-protected service
- Decryption of VPN traffic for users on compromised networks
- Compromised code-signing trust if the two code-signing intermediates are abused
- Extended cleanup timelines for embedded devices, IoT, and Linux distributions
Go cryptography engineer Filippo Valsorda called the cleanup “bigger than Heartbleed.” Heartbleed took years to remediate across the Internet, and this incident has even more heterogeneity because it involves trust stores in programming languages, containers, and embedded systems.
Mitigation and Recommendations
Immediate actions for defenders depend on the software stack in use. Most browsers have already blocked the intermediates. Other software requires updates or configuration changes.
Immediate Actions for Defenders
- Update Go to version 1.27.3 or 1.26.10 to reject chains using the compromised keys.
- Update Firefox to 158.0.1, ESR 115.43.1, or ESR 153.5.1 for OneCRL coverage.
- Update NSS to 3.131.1, which removes emSign ECC Root CA – G3.
- Update Python certifi to 2026.10.19, which drops the affected root.
- Update Rust webpki-roots to 1.0.10 for the same change.
- Audit Linux distribution trust stores and apply vendor patches.
- Restart or redeploy Docker containers and IoT devices after updating root bundles.
Monitoring Guidance
Monitor Certificate Transparency logs for unauthorized certificates chaining to the affected intermediates. Review network logs for unexpected certificate chains. Verify that VPN and remote-access infrastructure does not rely on the emSign ECC Root CA – G3.
Bottom line: Patch trust stores now. The browsers are protected, but the long tail of non-browser software and embedded devices remains exposed until administrators act.
Incident Summary
| CVE ID / Incident: | eMudhra Intermediate CA Private Key Compromise (CVE-2026-111943, CVE-2026-113470) |
| Affected Systems: | eMudhra emSign TLS and code-signing intermediates; Go, Firefox, NSS, Python certifi, Rust webpki-roots; Linux distributions; IoT and embedded devices |
| Disclosure Date: | October 17, 2026 (reported); October 20, 2026 (public confirmation) |
| Patch Status: | Updates released October 20, 2026; long-tail remediation ongoing |
References
- The Hacker News, “Eight eMudhra CA Keys Compromised, Triggering Emergency Fixes Across Browsers and Software,” October 20, 2026, https://thehackernews.com/2026/10/eight-emudhra-ca-keys-compromised.html, accessed October 20, 2026.
- Ars Technica, Dan Goodin, “The Internet goes on high alert after discovery of 8 compromised TLS certs,” October 20, 2026, https://arstechnica.com/security/2026/10/the-internet-goes-on-high-alert-after-discovery-of-8-compromised-tls-certs/, accessed October 20, 2026.
- Mozilla Security Blog, “Protecting Firefox users following the compromise of eMudhra intermediate certificates,” October 20, 2026, https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/, accessed October 20, 2026.
- Dennis Jackson, Mozilla cryptography engineer, “eMudhra we have a problem” advisory site, October 2026, https://emudhra.we-have-a-problem.com/, accessed October 20, 2026.