Full Breakdown
eMudhra’s Weak Certificate Keys Spark Global Trust Crisis and Business Exit
By Drooid · · How we work
Core Event
On October 17 2026 a security researcher disclosed that the private keys of eight eMudhra intermediate certificate authorities (CAs) were weak enough to be recovered in seconds. The eight CAs—six for TLS certificates and two for code-signing—had been created on April 30 2025 with single-byte private keys (4, 56, 66, 115, 155, 156, 230, 237) instead of the required 384-bit random values. Within hours Google and Mozilla blocked the intermediates, Apple and Microsoft followed, and eMudhra revoked the certificates on October 18 2026. India’s Ministry of Electronics and Information Technology (MeitY) formed a special investigative team, and eMudhra’s board announced on October 22 2026 that it would exit its global SSL/TLS certificate business.
Background & Context
Digital certificates act as identity cards for websites. A trusted root CA signs intermediate CAs, which issue end-entity certificates to sites or software. eMudhra, a Bengaluru-based firm licensed by the Controller of Certifying Authorities (CCA), runs two services: Indian-regulated Digital Signature Certificates (DSCs) and an international web-security business that supplies TLS and code-signing certificates trusted by major browsers.
Official Statements & Responses
- eMudhra (Oct 21 2026) said a flaw in its key-generation ceremony produced weak keys, that its infrastructure was not breached, and that it revoked the eight CAs within 14 hours.
- MeitY took “serious note” of the incident, formed a special team, and said DSC and eSign services remain unaffected.
- CERT-In warned that recovered keys could enable attackers to forge certificates and issued mitigation guidance.
- Google updated Chrome to block the compromised keys and scheduled removal of the emSign ECC Root CA-G3 on Oct 27 2026.
- Mozilla added the six TLS intermediates to its OneCRL blocklist on Oct 17 2026.
- Cloudflare rolled out protections on Oct 19 2026 and reported no evidence of active exploitation.
Conflicting Reports & Gaps
- eMudhra claimed none of the eight intermediates issued end-entity certificates, yet some sources reported that one TLS intermediate had been deployed in production.
- Google said no TLS certificates chaining to six of the intermediates appeared in Certificate Transparency logs before the block, while CERT-In cautioned that attackers could still forge certificates for systems that do not check those logs.
- The timeline for root-certificate removal varies: Chrome’s scheduled removal is set for Oct 27 2026, whereas earlier reports mentioned an imminent rollout without a specific date.
What’s Next
- Chrome will remove the emSign ECC Root CA-G3 from its trust store on Oct 27 2026.
- MeitY’s special team will continue its investigation, with a full root-cause report expected from eMudhra after the audit.
- eMudhra will replace affected customer certificates free of charge and maintain revocation services until all legacy certificates expire.
- Organizations using eMudhra-issued certificates must audit trust stores, update browsers and non-browser applications, and migrate to alternative CAs where necessary.
