eMudhra's Weak Certificate Keys: What to Do

This one sounds technical, but it touches anyone who uses a browser. A certificate authority called eMudhra created eight website-security certificates whose secret keys were so weak that one of them was literally the number 4. Browsers have already moved to block them. I've gone through the statements from Google, Mozilla and eMudhra itself, and here's the short version.

What happened

On 17 October 2026, a security researcher reported that eight intermediate certificates from eMudhra, a Bengaluru-based certificate authority, had private keys anyone could recover. These intermediates sit under eMudhra's emSign ECC Root CA - G3, and they were trusted by all the major browsers. With one of those keys, an attacker could in theory create a certificate that impersonates any website.

How weak were they? Ars Technica reports the keys were supposed to carry around 384 bits of randomness, but the actual values were tiny numbers: 4, 56, 66, 115, 155, 156, 230 and 237. Cracking them takes milliseconds.

In its own statement, eMudhra says the keys came from a key-generation ceremony on 30 April 2025, where a flaw in one wrap/unwrap step produced a second, weak set of keys, and those were the ones published. It revoked all eight on 18 October. The company says seven were never used in production, the one that was had not issued a single certificate, and it knows of no evidence the keys were exploited before disclosure. Ars also reports that eMudhra is now leaving the public TLS certificate business.

Why it matters

The big browsers reacted fast. Google says Chrome pushed a block within two hours of the report on 17 October, and Android got an equivalent fix through Google Play Services. Google is also pulling the emSign ECC Root CA - G3 root out of the Chrome Root Store, with that change expected to reach all devices on 27 October 2026. Mozilla blocked the certificates in Firefox the same day and followed with Firefox 158.0.1 and ESR releases 115.43.1 and 153.5.1.

The part I'd worry about is everything that isn't a browser. Google says no certificates from these intermediates ever showed up in public Certificate Transparency logs, which is reassuring. But the researcher's disclosure site warns that software which doesn't use browser-style revocation lists, think IoT devices, older Linux systems and apps with their own certificate bundle, needs an actual update to stop trusting them. It's serious enough that Fedora counted it among the blockers that pushed Fedora 45's release to a new target of 3 November.

What to do

• Restart your browser and your phone. On Android, Google says a restart pulls the Play Services fix right away.
• Update Firefox if you've turned off automatic certificate updates, and install your OS updates, especially the ca-certificates package on Linux.
• Open the disclosure site in each browser or tool you rely on. It tells you whether that client still accepts the bad intermediates.
• If you run a website with a certificate that chains to emSign ECC Root CA - G3, replace it with one from another provider before 27 October, or Chrome visitors will start seeing errors.

If you like controlling what your devices trust at the network level, my guide to Private DNS on Android is a good next read.

Sources: Google Security Blog, eMudhra, Mozilla (via eMudhra's statement), eMudhra Intermediate CA Compromise, with reporting from Ars Technica and XDA.