eMudhra Keys Compromised, Threatening Browser Trust

On October 20, researchers announced that the private signing keys belonging to eight intermediate certificate authorities operated by eMudhra had been compromised. The breach was confirmed by both Mozilla’s Root Certificate Program and Google Chrome’s root program, leading each organization to immediately revoke trust in those keys and inform users that browsers would no longer accept certificates issued using them.¹

Intermediate CAs play a pivotal role in public‑key infrastructure: they sign certificates that websites present during HTTPS handshakes, allowing browsers to verify that a site is authentic. If an attacker obtains a private key from such a CA, they can create a valid certificate for any domain the browser trusts, effectively enabling man‑in‑the‑middle attacks against unsuspecting sites. In this case, possession of the eMudhra keys could allow issuance of certificates for any website whose chain includes one of these intermediates, potentially compromising traffic across millions of sites worldwide.

The incident echoes the DigiNotar compromise of 2014, when Comodo’s intermediate CA suffered a similar breach and forged SSL/TLS certificates were used to distribute malware widely. That event forced browsers to roll back trust in affected roots over several days or weeks; revocation lists had to be disseminated globally, and many systems required manual updates before full remediation. Unlike that earlier episode, modern browsers now employ automated responses through certificate transparency logs, which enable faster detection than previously possible with manual inspection only—the attack vector remains unchanged until all clients update their trust stores.

Because Mozilla and Google confirmed the issue simultaneously, it suggests widespread use of these eMudhra intermediates across different ecosystems. High‑profile websites—particularly those relying on Indian infrastructure or using eMudhra as part of their PKI—may have been impacted before the breach was detected. The rapid response by root programs underscores how critical timely revocation is: if an attacker can generate fraudulent certs during the lag between key exposure and global revocation, they may intercept sensitive data, inject malicious code, or impersonate legitimate services.

Beyond web browsing, the threat extends to IoT devices and other software that rely on trusted CAs for secure communication. Many such devices are not patched quickly enough due to limited resources at end users’ disposal, meaning compromised keys could persist longer than anticipated. This scenario raises concerns about automated key management practices within Certificate Authorities themselves. If CA operators fail to detect internal leaks promptly, the entire PKI chain becomes vulnerable.

Organizations should verify that their operating systems reflect the latest revocation lists from Mozilla and Chrome, monitor issued certificates via public logs, and audit any custom certificate usage in corporate environments. Additionally, security teams might consider implementing stricter controls around private key storage, including hardware security modules (HSMs) and multi‑factor authentication for access to signing servers.

The eMudhra incident serves as a stark reminder that trust anchors—intermediate CAs—are only as strong as their operational hygiene. While browsers now react faster thanks to transparency logs, the window of vulnerability remains significant until all clients update. Vigilance over key lifecycle, coupled with rapid patching of root stores, is essential to prevent attackers from turning compromised intermediates into widespread TLS fraud tools.