Eight eMudhra intermediate CA keys exposed; browsers block them, other tools may not

What happened

The private keys of eight eMudhra intermediate certificate authorities were generated so weakly that anyone can compute them from the public certificates. Six of the intermediates are for TLS and two are for code signing. The keys were not stolen. Mozilla recovered them independently, and it says multiple other people did too.

A researcher known as Wayne reported the problem on 17 October and proved control of all eight keys. Chrome and Firefox blocked the intermediates within hours. eMudhra revoked them on 18 October and Sectigo revoked its cross-signed copies on 19 October. Microsoft and Apple products now block them as well. Mozilla then moved to remove trust in emSign ECC Root CA - G3 entirely, and Chrome is following.

eMudhra says the flaw was in its key generation step, that its infrastructure was not compromised, and that it has no evidence the weak keys were used before disclosure. No certificate issued from these intermediates has been seen in Certificate Transparency logs, and no abuse is confirmed. Tools that do not enforce Certificate Transparency, such as curl and most language runtimes, would not notice an unlogged certificate.

Browsers already block these intermediates. The risk on a developer Mac is software that checks certificates without checking revocation, or that ships its own root list. Removing the root also breaks legitimate sites that chain to it, and the sources disagree on how many certificates that affects.

Timeline

1. 17 Oct 2026
   18:05 UTC

   Chrome Root Program received the report of the compromise.[6]

2. 17 Oct 2026, 19:45 UTC

   A Chrome CRLSet update blocking the six TLS intermediates was in place.[6]

3. 17 Oct 2026, 20:06 UTC

   Mozilla received the report.[2]

4. 17 Oct 2026, 21:48 UTC

   Mozilla recovered the private keys independently.[2]

5. 17 Oct 2026, 22:59 UTC

   Firefox OneCRL distrust of the certificates completed.[2]

6. 18 Oct 2026
   09:38 UTC

   eMudhra marked the eight certificates as revoked.[2]

7. 19 Oct 2026
   17:00 UTC

   Cloudflare became aware of the compromise and began its assessment.[4]

8. 20 Oct 2026
   13:06 UTC

   Mozilla announced emergency removal of trust in emSign ECC Root CA - G3.[2]

9. 20 Oct 2026, 16:27 UTC

   eMudhra stopped issuing from intermediates chaining to emSign ECC Root CA - G3.[2]

Who is affected

• Developers on a Mac using tools that check certificates without revocation: the built-in curl, git, python3 and openssl read the system bundle at /etc/ssl/cert.pem.
• Users of runtimes and tools that ship their own root lists, such as Python certifi, Node.js, Go and Java, until updated.
• Go programs built before the fixed Go release, since they must be rebuilt to reject the keys.
• Operators of servers whose certificates chain to emSign ECC Root CA - G3, which will stop working once Chrome's removal reaches devices.
• Teams running containers, mutual TLS or custom origin certificates, which may need to update their own trust stores.
• Browser users on current versions are covered. Firefox needs action only if Remote Settings is disabled or blocked.

How to check

1. Check whether the system bundle used by the built-in curl, git, python3 and openssl still lists emSign ECC Root CA - G3 or AAA Certificate Services. If so, those tools still trust the chain.
2. Check the installed versions of Python certifi, Node.js, Go, Java and any Electron or Docker Desktop apps against the fixed versions. The disclosure site run by Mozilla's Dennis Jackson has a crowdsourced list of patched versions.
3. Confirm that Go binaries were rebuilt with the fixed Go release.
4. The disclosure site also offers test sites. A certificate error from a client means it no longer trusts the compromised intermediates. These are test sites, not indicators.
5. Validate through the application's real TLS path, because a working browser does not show that a background service is protected.

What to do

1. Update macOS and your browsers to the latest versions.
2. Update the runtimes and tools that ship their own root bundles, rebuild Go programs with a fixed Go, and rebuild affected container images.
3. Restart or redeploy long-running processes so they reload their trust stores.
4. Do not resolve certificate errors after patching by turning off verification.
5. The disclosure site explains how to remove the affected roots from /etc/ssl/cert.pem. That edits a system file, so read it carefully first.
6. If your servers use certificates chaining to emSign ECC Root CA - G3, replace them before Chrome's removal reaches all devices. That is planned for 27 October.
7. eMudhra says it offers replacement certificates, including ones issued by Sectigo.