Technology
Weak eMudhra certificate keys exposed non-browser TLS clients to forged certificates
Eight eMudhra certificate-authority keys were generated with only one-byte private values, making them recoverable almost instantly from public certificates. Browsers moved to block the affected intermediates and roots, but many non-browser clients do not check revocation or Certificate Transparency by default. That leaves software such as package managers, CI systems, APIs and embedded devices potentially exposed until their trust stores are updated. The incident report later attributed the error to a faulty ceremony script and human selection mistake.
Editorial summary · Publisher article
What matters
- All eight affected keys could be brute-forced in at most 255 trials.
- The certificates covered six TLS intermediates and two code-signing authorities.
- Updated browsers had stronger protections than many command-line and server clients.
- The recommended response is to update trust stores, packages and rebuild affected images.
Context & caveats
- Exposure depends on client trust-store updates and the possibility of certificates being misused during the 17-month window.
Why this made the edition
The detailed account explains the cryptographic failure, affected certificate types, client exposure, browser mitigations and remediation, with an update attributing the mistake to a certificate-generation process bug.
Source material