Full Breakdown
Global Web-Trust Shock: Eight eMudhra Intermediate Certificates Compromised
By Drooid · · How we work
The Compromised eMudhra Intermediate Certificates
Eight intermediate certificates issued by Indian CA eMudhra contained private keys that were single-byte numbers—4, 56, 66, 115, 155, 156, 230 and 237—rather than the required 384-bit random values. Generated on April 30 2025, the keys were recovered in less than a second, exposing a path for attackers to forge HTTPS or code-signing certificates.
Background and Trust Infrastructure
eMudhra’s root CA is trusted by major browsers and OS vendors. The compromised intermediates belonged to the “emSign” hierarchy and were used to issue over 60 million certificates worldwide. Only one of the eight intermediates had ever been deployed in production and none issued certificates to external customers.
Timeline of Discovery and Response
| Date | Event |
|---|---|
| April 30 2025 | Weak-key intermediates created. |
| Oct 17 2026, 20:06 UTC | Mozilla received the report. |
| Oct 17 2026, 19:45 UTC | Chrome Root Program pushed a CRLSet update blocking six TLS intermediates. |
| Oct 17 2026, 22:59 UTC | Mozilla distributed a OneCRL update blocking all eight intermediates. |
| Oct 18 2026 | eMudhra revoked the eight certificates. |
| Oct 19 2026 | Apple released updates to block the certificates. |
| Oct 20 2026 | Microsoft updated its trust store; Mozilla removed one eMudhra root from Firefox. |
| Oct 21 2026 | eMudhra’s shares fell 20 % to 432 rupees. |
Technical Details and Scale
- Key values: 4, 56, 66, 115, 155, 156, 230, 237.
- Certificates affected: Six TLS intermediates and two code-signing intermediates.
- Potential impact: Possession of any key would allow issuance of certificates accepted by browsers, enabling man-in-the-middle attacks.
- Actual misuse: Transparency logs show no fraudulent certificates issued; no public evidence of exploitation.
- Customer exposure: Approximately 30 000 live website certificates may need re-issuance; enterprise-signature services remain unaffected.
Official Statements and Industry Response
- eMudhra emphasized that only the eight intermediates were affected and that its root keys remain secure.
- Mozilla blocked the certificates via OneCRL and removed one eMudhra root from Firefox.
- Google: Updated Chrome’s CRLSet to block the six TLS intermediates, extending protection to Android.
- Apple and Microsoft: Issued rapid trust-store updates on Oct 19 2026 and Oct 20 2026.
- Open-source runtimes (Go, Python, Rust) released patches rejecting the compromised keys.
Conflicting Reports and Open Questions
The exact cause of the weak keys remains unconfirmed, and the point at which they entered production is unclear.
What’s Next for Users and Operators
- Browser users: Keep browsers and OSes up to date; revocation updates are already applied.
- Server and device administrators: Audit trust stores, especially on legacy Linux, IoT devices, and custom CA bundles. Apply language-runtime patches.
- eMudhra: Continues its investigation, re-verifies key-generation ceremonies, and migrates customers to certificates signed by unaffected roots. Further updates will follow.