The private keys for eight eMudhra intermediate CA certificates were compromised, and the reason is almost worse than the breach itself: weak key generation left them vulnerable to being cracked in milliseconds.

These aren’t some obscure certificates you’ve never heard of. eMudhra’s intermediate CAs chain to roots trusted by Mozilla, Microsoft, Apple, and Chrome. If your software bundles trusted certificates, anywhere in the stack, it needs an update.

What Actually Happened

Certificate authorities are supposed to generate keys with sufficient entropy that cracking them is computationally infeasible. eMudhra apparently didn’t do that. The technical details point to catastrophically weak random number generation during key creation.

When a CA’s private key is compromised, an attacker can issue valid certificates for any domain. Those certificates will be trusted by browsers, operating systems, and any application that relies on the compromised CA’s chain of trust. This is a fundamental break in PKI.

What Needs Updating

Linux distributions need to update their ca-certificates packages. The Python ecosystem is already moving: uv 0 has been updated. But this goes deeper than package managers.

Any application that bundles its own certificate store is potentially affected. That includes containerized applications, embedded systems, IoT devices, and plenty of enterprise software that ships with certificates baked in.

A GitHub repository is tracking software updates. If you maintain software that validates TLS connections, check it.

The Broader Problem

This isn’t the first time weak key generation has broken PKI, and it won’t be the last. The Debian OpenSSL bug in 2008 produced predictable keys. The ROCA vulnerability in 2017 affected millions of smart cards and TPMs. Each time, we discover that random number generation is harder than it looks.

The difference here is speed. “Cracked in milliseconds” means these keys had so little entropy that brute force wasn’t even necessary. That suggests a fundamental implementation failure in the key generation process.

For developers, the immediate action is clear: update your certificate bundles. The longer-term lesson is that trust infrastructure is only as strong as its weakest implementation, and sometimes that weakness is measured in bits.