A security researcher recently revealed that eight intermediate certificates issued by the certificate authority (CA) eMudhra were secured with critically weak private keys. These keys, which were intended to be massive random numbers, were instead found to be very small integers, such as 4, 56, and 115. Because the security of elliptic-curve cryptography relies on the difficulty of reversing a public key to find its corresponding private key, these 'single-byte' keys were trivial to crack. A researcher was able to recover all eight keys in less than a second using commodity hardware, effectively compromising every certificate those CAs could ever issue.
This image provides a visual representation of the eMudhra CA security breach described in the article.
The vulnerability stems from a human or script error during the key generation ceremony in April 2025. Instead of generating a 384-bit random number, the system produced keys with only a few bits of entropy. While the resulting public keys appeared structurally valid and passed all standard checks, they were inherently insecure. Major browser vendors, including Google, Apple, Microsoft, and Mozilla, have since moved to block these intermediate certificates and, in some cases, remove the eMudhra root from their trusted stores. However, the researcher notes that while browsers often enforce Certificate Transparency (CT) to detect such mis-issuances, many other software components do not.
The scope of the risk extends beyond web browsing to a vast ecosystem of non-browser clients. Tools like `curl`, Python, Node.js, and various package managers typically trust a local CA bundle and may not check for certificate revocation or CT logs. This leaves systems such as IoT devices with frozen firmware, CI/CD pipelines fetching dependencies, and server-to-server API calls vulnerable to interception. Because these devices often lack easy update paths, they may continue to trust the compromised certificates until their expiration in 2039. The incident highlights a critical gap in the Public Key Infrastructure (PKI) where the sheer scale of the client ecosystem makes it difficult to contain a compromise that exists in the 'trust' of the software rather than a stolen file.