eMudhra revokes 8 more intermediate CAs (16 total) after Python key-ceremony script mishandled private keys; browsers distrust chains
Matéria consolidada. Reúne 2 matérias que o Tifon tinha publicado separadamente sobre a mesma história. A IA reescreveu o relatório com o que as 2 fontes trouxeram em 12/11/2026 00:01; os links antigos trazem para cá.
eMudhra has revoked eight more intermediate CA certificates after its investigation into a certificate security incident found improper private key handling during a key ceremony. According to bleepingcomputer.com (the most recent source, 2026-11-11), this brings the total of affected intermediate CAs to sixteen, including eight earlier ECDSA CAs whose keys were extremely weak and easily recoverable. The root cause was a flawed in-house Python script used to transfer keys between HSMs. The affected CAs were actively used to issue TLS and code-signing certificates, and customer certificates have been replaced or migrated. No evidence of malicious use of the keys has been found so far (bleepingcomputer.com, thehackernews.com). Major browser and OS vendors are distrusting the affected chains, and eMudhra will exit the publicly trusted TLS certificate business and has commissioned an independent review (bleepingcomputer.com).
Detalhes técnicos
- The script was used in a key ceremony on April 30, 2025. It read private keys out of the HSMs into memory and rebuilt them for transport (thehackernews.com).
- A coding error truncated the private key values. For the ECDSA keys, this reduced them to a single byte, making them trivially recoverable (bleepingcomputer.com).
- The RSA keys were not cryptographically weakened, and they still produced valid signatures. However, they were exposed outside the HSM memory protection, so eMudhra cannot demonstrate that they were handled in line with its policies (thehackernews.com, bleepingcomputer.com).
- eMudhra detected invalid CRL signatures in June 2025 and then ran a detailed incident review (thehackernews.com).
- The script was specific to this incident. Keys are normally generated in place without transfer (thehackernews.com).
- The RSA CAs were revoked with reason code cessationOfOperation rather than keyCompromise, because no cryptographic weakness was exploited (thehackernews.com).
Remediação
- Browser vendors (Microsoft, Chrome, Firefox, Apple) have announced distrust timelines for all certificates chained to the affected CAs, including emSign Root CA - G1. These start on November 16 and continue into late November (thehackernews.com).
- Defenders should review the status of any certificates issued under these CAs and move to certificates from alternative providers (thehackernews.com).
- eMudhra has committed to improving its key management and script handling and to publishing its scripts for transparency (thehackernews.com). It also commissioned an independent review (bleepingcomputer.com).
Relatos divergentes
- Scope: thehackernews.com describes the revocation of 8 intermediate CAs, with the truncation affecting RSA keys. bleepingcomputer.com, the more recent source, says these are 8 additional CAs on top of 8 earlier ECDSA CAs, for 16 in total. The bleepingcomputer.com framing is more current.
- Block status: thehackernews.com describes distrust timelines starting November 16. bleepingcomputer.com says major browsers and OS vendors have already blocked the certificates. The exact enforcement dates are unconfirmed.
Linha do tempo
-
eMudhra revokes 8 additional intermediate CA certificates in private key mishandling aftermath
ler a análise desta fonte ocultar
Certificate authority eMudhra has revoked eight more intermediate CA certificates after its investigation into a certificate security incident revealed improper private key handling during the certificate generation process. This brings the total affected intermediate CAs to sixteen, including eight previously compromised ECDSA keys that were extremely weak and easily recoverable. The root cause was a flawed Python script used to transfer keys between hardware security modules (HSMs), which reduced ECDSA keys to a single byte and exposed RSA keys outside the HSM memory protection. Although the RSA keys were not cryptographically weakened, their handling violated eMudhra's security policies, leading to their revocation. The compromised certificates were actively used to issue TLS and code-signing certificates, and customer certificates have been replaced or migrated. Major browsers and OS vendors have blocked the affected certificates. eMudhra will exit the publicly trusted TLS certificate business and commissioned an independent review to improve its key management practices. No evidence of malicious use of compromised keys has been found so far.
-
eMudhra Revokes 8 Intermediate CAs Following Key Handling Flaws Despite No Key Weakness
ler a análise desta fonte ocultar
eMudhra's recent incident involves the revocation of 8 intermediate CAs after a Python script used during a key ceremony improperly handled private keys, leading to potential security concerns. Although the keys were not weakened cryptographically, the company cannot demonstrate that private key material was managed in compliance with their policies. The incident traces back to a mistake during a key transfer process, where private keys were read into memory, risking exposure. Despite the absence of malicious misuse, browsers and certificate authorities are removing trust from affected certificates.
Technical Details
The incident stems from a flaw in an in-house Python script used during a key ceremony on April 30, 2025. The script read private RSA keys from HSMs into memory and rebuilt them for transport, which, due to a coding error, truncated the private key values for 8 CAs. Although these keys still generated valid signatures, the process did not meet the company's policy requirements for handling private key material, leading to their revocation. The company conducted a detailed incident review after detecting invalid CRL signatures in June 2025.
Fix Details
The company has revoked the 8 compromised CAs with reason code cessationOfOperation, rather than keyCompromise, indicating no cryptographic weakness was exploited. The Python script used was limited to this incident; normally, keys are generated in place without transfer. The incident resulted from reading private keys into memory during transport rather than a cryptographic attack.
Remediation
eMudhra has committed to reviewing and improving their key management and script handling procedures, including publishing their scripts for transparency. Browser vendors like Microsoft, Chrome, Firefox, and Apple have announced timelines to distrust certificates from the affected roots, starting from November 16 and continuing into late November, to phase out the trust for all certificates chained to these compromised CAs (including emSign Root CA - G1). Users are advised to review certificate status and update to new certificates issued by alternative providers.