eMudhra Faces Certificate Revocation Following Private Key Compromise
Eight intermediate certificate authority keys belonging to eMudhra were compromised due to a vulnerability allowing the keys to be recovered. In response, browser vendors and trust store operators have moved to block these specific certificates.
Published Oct 22, 2026, 12:06 AM · Last verified Oct 22, 2026, 12:06 AM
What Happened?
Eight intermediate certificate authority keys issued by eMudhra were found to be cryptographically vulnerable, allowing for their recovery. Consequently, major browser vendors and trust store operators have initiated actions to block the affected certificates to protect users.
Who Was Affected?
eMudhra, a certificate authority, is the primary organization affected by this security lapse.
When Did It Happen?
The incident was reported on October 21, 2026.
How Did the Attack Happen?
The private keys associated with the intermediate certificates were compromised through a technical failure that rendered them recoverable.
What Information Was Compromised?
Private keys related to eight distinct intermediate certificate authorities were exposed.
Who Is Responsible?
Not yet disclosed in the sources reviewed.
Current Investigation and Response?
Browser vendors and trust stores are currently blocking the impacted certificates to mitigate the risk of unauthorized issuance.
What Organizations and Individuals Can Learn?
Entities relying on public key infrastructure should prioritize rigorous security auditing of key generation processes. Organizations must ensure that intermediate CA keys are stored and managed using hardware security modules that prevent key recovery or unauthorized extraction.
Key takeaways
- Eight eMudhra intermediate certificates are being blocked due to key compromise.
- The vulnerability allowed for the recovery of private keys.
- Browser trust stores are actively mitigating the threat by revoking or blocking the affected certificates.
Protection recommendations
- Verify if any systems rely on certificates issued by the compromised eMudhra intermediates.
- Update browser and root trust stores to ensure the latest revocation lists are applied.
- Implement high-security storage for cryptographic keys, such as FIPS-compliant Hardware Security Modules.
Incident timeline
Oct 21, 2026
First reported by SecurityWeek
Oct 21, 2026
Additional source: Help Net Security
Sources
- Browsers Block eMudhra Intermediate CAs Over Recoverable Private Keys · SecurityWeek
- eMudhra security blunder left trusted CA signing keys exposed to anyone · Help Net Security
This report was drafted with AI from the headline and excerpt of the sources above and reviewed by an editor. See our AI disclosure and corrections policy. Based on the headline and excerpt published by SecurityWeek.