Mozilla received a report on the evening of October 17 that private keys behind eight eMudhra intermediate certificates were compromised. Cloudflare’s summary of the impact is blunt: whoever holds those keys can mint a certificate for any domain and impersonate the server.
Dennis Jackson of Mozilla’s cryptography engineering team disclosed the finding on October 20. By then Chrome, Apple and Mozilla were all moving to distrust the intermediates, eMudhra had revoked them, and a long list of open source projects had shipped updates that stop honouring certificates chained to them.
The keys were guessable
Researcher Scott Helme recovered the keys from public certificates on his own laptop. One was the number 4. Another was 56, another 115, and other researchers added 66, 155, 156, 230 and 237. A P-384 key is supposed to be a random 384-bit value with roughly 10 to the 115th power of possibilities. A single digit offers a few.
eMudhra claims more than 60 million certificates issued. The company did not respond to press questions about the incident or its key handling.
Where the exposure lingers
Browser makers are built to detect and reject the bad anchors, so patched browsers are largely covered. The problem is everything downstream that pins or trusts those intermediates directly, from appliance firmware to internal service meshes, which will not consult a browser revocation list. Those teams need to inventory their trust stores and test whether any chain terminates at an eMudhra intermediate.
The event also sharpens a question every PKI owner should answer before an auditor asks it: what process generated those keys, and can you prove it? A weak random number generator is invisible for years and then catastrophic in a single afternoon.
