GoKawiileMudhra certificate authority keys found to be trivially weak numbers like 4 and 56
A security researcher discovered that eight eMudhra intermediate certificate authority private keys, including six TLS issuing CAs and two code-signing CAs created in April 2025, were generated as tiny single-digit or small numbers rather than proper random 384-bit values. Browser vendors moved quickly: Chrome blocked the certificates via a CRLSet update and Mozilla followed via OneCRL, with Mozilla later shipping an NSS update to remove the eMudhra root and Chrome confirming removal in its Root Store v43.
GoKawiil's interpretation of the reporting above, not reported fact.
The flaw undermines the entire cryptographic guarantee behind elliptic-curve keys, since security depends on the private key being effectively unguessable, and a key like '4' can be recovered instantly rather than requiring billions of years of computation. Because the compromised intermediates were also cross-signed by Sectigo's AAA root, the problem could extend trust chains beyond eMudhra alone, suggesting remediation may be more complex than removing a single root. The episode raises questions, according to researchers quoted in the discussion, about how such weak keys passed any internal validation at a certificate authority.
- eMudhra's CA private keys were absurdly small numbers (e.g., 4, 56, 115) instead of proper random 384-bit values.
- Chrome and Mozilla both blocked the affected certificates within hours and later moved to remove the eMudhra root entirely.
- Cross-signing by Sectigo's AAA Certificate Services root complicates full containment of the compromised trust chain.
Source: scotthelme.co.uk — Scott Helme, 2026-10-21
Published there as: “Eight Bits of Trust; eMudhra's CA keys cracked in milliseconds”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.