Renews.
← IT

eMudhra revokes eight more CAs after script bug weakens keys

eMudhra revoked eight intermediate certificate authorities after a Python script truncated their private keys to one byte during generation.

IT·3 sources
Photo: AlfLucio / Pixabay

eMudhra has revoked eight additional intermediate certificate authorities following an investigation into improper private key handling. The company stated that a single line in an in-house Python script cut the private keys of these eight CAs to one byte, even though the script did not directly weaken the keys. The script retrieved the RSA keys from eMudhra's hardware security modules. Because logs and files from the ceremony computer cannot reliably show how the material was handled, eMudhra cannot demonstrate that the private key material was handled in compliance with its own rules.

The incident traces back to a key ceremony on April 30, 2025, where eMudhra generated sixteen CA keys on Utimaco HSMs. To move keys between HSMs from different vendors, eMudhra used a custom Python script to wrap and unwrap the keys. After the transfer, the script read each private key out of the HSM into memory and rebuilt the key from that copy. For the eight ECDSA keys, a single line in the read-back process truncated the private value to its leading byte. The rebuilt weak keys carried a label almost identical to the original, allowing them to be sent for signing and certification. eMudhra calculated that the smallest of the eight compromised keys is 4 and the largest is 237.

Six of the revoked CAs were used for website TLS certificates, while two were used for code signing. Four of these CAs had been put into production in May. eMudhra's list of revoked certificates includes 195 certificates from these eight CAs, with 29 for its own domains. Invalid CRL signatures in June 2025 served as an early sign of the same fault, which eMudhra fixed by re-signing the lists with keys that matched the certificates.

Previously, eMudhra declared these eight CAs unaffected on October 19, stating they went through a different path than the keys compromised in October. However, the company reached its conclusion about the RSA key handling in early November after discussions with browser root programs. eMudhra revoked the eight RSA CAs late last week using the reason code cessationOfOperation, rather than the CA-compromise code used for the first eight revocations on October 18.

Sources

Every sentence of this story was checked against facts quoted from these articles. How we make the news

Spotted an error? Tell us

Sign in

Keep the stories you like in your favorites.

Forgot your password?

No account?