Skip to content
Start with Identity
News

Browsers block eight eMudhra intermediate CAs after their private keys leak

A researcher reported on October 17 that the private keys of eight eMudhra (emSign) intermediate CAs, six for TLS and two for code signing, were compromised. Chrome and Firefox blocked them within hours; Apple, Microsoft and Go followed, and Mozilla is removing the emSign ECC root.

By SWI Community TeamOct 20, 2026

Mozilla said on October 20 that the private keys of eight intermediate certificate authorities run by eMudhra, the Indian CA that sells under the emSign brand, had been compromised. A researcher reported it on Saturday, October 17; Chrome blocked the six TLS intermediates through CRLSet at 19:45 UTC and Mozilla pushed a OneCRL block to Firefox by 22:59 UTC. The other two are code-signing CAs. Apple blocked the certificates on October 19 and Microsoft on October 20, according to The Hacker News. Mozilla's NSS 3.131.1 removes the emSign ECC Root CA - G3 that issued the TLS intermediates, Go 1.27.3 and 1.26.10 reject chains containing any of the eight keys, and the intermediates also exist as Sectigo cross-signed copies. How the keys left eMudhra has not been disclosed.

Why it matters

A CA key is an identity factory: whoever holds it can mint a certificate that proves to a client it is talking to any domain, or that code came from any publisher. Chrome found no TLS certificate from these intermediates in Certificate Transparency logs, so browsers that require CT were not exposed. Most other software is less protected.

Go binaries and anything built on Python's certifi bundle do not check revocation, so they keep trusting these chains until rebuilt or until their root bundle updates. Rebuild Go services on the fixed releases, update certifi (2026.10.19), Rust webpki-roots and OS trust stores, and inventory where your own PKI clients pin or bundle roots. If you buy certificates from eMudhra, plan to move chains now, since root removal also breaks legitimate certificates. Teams that already automate certificate lifecycle work can swap issuers in days rather than weeks.

Source: Mozilla Security Blog

Last reviewed By SWI Community TeamSuggest a correctionHow we research
Independent analysis. No vendor sponsorship. Editorial policy · Report a correction