Someone Left the Internet's Master Keys Under the Doormat

Someone Left the Internet's Master Keys Under the Doormat

Eight intermediate keys fall at once

The private keys behind eight intermediate certificates of eMudhra, an India-based certificate authority, are compromised. Anyone holding them could mint a certificate for any website on Earth that browsers would accept without complaint — a skeleton key for the HTTPS trust system. Six of the eight issued website TLS certificates and two issued code-signing certificates. According to Dark Reading, the six TLS intermediates were the EM DV, OV and EV TLS CAs in G3B and G3C variants under emSign Root TLS CA - G3, with the two code-signing intermediates under emSign Root CS CA - G3, all chaining to the emSign ECC root trusted in every major root store.

A researcher signs his warning with the stolen keys

A researcher going only by "Wayne" reported the compromise to the browser trust programs on October 17. As proof, he stood up the demo site emudhra.we-have-a-problem.com bearing the message "We have a problem here — Wayne," signed one by one with all eight private keys. Ars Technica reports that Google's Chrome Root Program got the report at 18:05 UTC on October 17 and finished corroborating it at 19:45; Mozilla learned of it at 20:06. The demo even included a forged certificate for q3k.google.com, reported by heise, showing the counterfeit-to-trusted pipeline worked end to end.

The keys turned out to be integers under 256

eMudhra blamed a scripting error from April 2025 that generated a second, weaker set of keys whose similar labels got them mistakenly picked for signing. Per Mozilla's incident record, the eight came from a batch of 24 intermediates minted in a single key ceremony on April 30, 2025. A P-384 private key should be a random number of astronomical size; these were all integers below 256, crackable by trying at most 256 guesses. One developer recovered all eight in 11 milliseconds, and Mozilla reproduced the recovery itself in under two hours. GeneratorLabs adds that Sectigo cross-signed the batch two weeks later, spreading the trust even wider.

A 17-month window no one can audit

From April 2025 to October 2026 — 17 months — anyone who ever looked at these certificates could have derived the keys in milliseconds on commodity hardware, and that history cannot be audited. As security researcher Scott Helme puts it, there is no way to know whether anyone did. No in-the-wild exploitation is known: Cloudflare says it found none on its own services, and heise judges ordinary users were probably never at risk. But the danger is trust itself — had the keys been abused, victims would have seen a reassuring "secure" indicator while passwords and banking details were intercepted or altered.

Browsers block at speed, users just update

eMudhra has revoked all eight certificates. Apple blocked them on October 19 and Microsoft on October 20. Mozilla pushed blocks through OneCRL to all standard Firefox users within three hours of the report (by 22:59 UTC on October 17), then shipped Firefox 158.0.1 plus ESR 115.43.1 and 153.5.1, and updated NSS to 3.131.1 to remove the offending root; Chrome landed its block the same evening and plans to drop the emSign root, and the Go project blocked the certificates too. Cloudflare finished its CDN and server-side Zero Trust mitigations at 19:20 UTC on October 20 and shipped tunnel client cloudflared 2026.10.2. Ordinary users need only update their browsers; admins running mutual TLS or Full (strict) origin encryption should review their trust stores and certificates.