eMudhra intermediate CA keys compromised due to flawed generation

On October 17, 2026, a security researcher disclosed that the private keys for eight intermediate Certificate Authority (CA) certificates issued by eMudhra had been compromised. This breach affects trust chains rooted in programs managed by Mozilla, Microsoft, Apple, and Chrome, impacting a wide range of downstream software and devices.

The compromise was not caused by a traditional server intrusion or phishing attack. Instead, the root cause was a critical error in how the CA generated the cryptographic keys. The private keys were mathematically recoverable from the public certificates themselves, meaning any actor with access to the public data could derive the secret keys needed to sign fraudulent certificates. This vulnerability existed since the certificates were created in April 2025.

What happened

The issue came to light when a reporter named Wayne demonstrated the compromise to Root Program Teams. To prove possession of the private keys, Wayne signed a specific message using the private key of each of the eight affected intermediate CAs. He provided the certificates, public keys, and signatures in a file named "Wayne proof.zip". This cryptographic proof allowed verifiers to confirm that the private keys were indeed accessible to unauthorized parties without needing to exploit a live system.

Following the disclosure on October 17, major browser vendors acted quickly to protect users. Firefox and Chrome blocked the compromised certificates starting on the same day. Apple followed suit, blocking the certificates on its devices by October 19. The eMudhra CA also revoked the compromised intermediate certificates. However, revocation alone is not sufficient for all systems. Many non-browser clients do not check Certificate Revocation Lists (CRLs) or Online Certificate Status Protocol (OCSP) responses in real time. These clients require software updates to remove the compromised roots or intermediates from their local trust stores entirely.

Key details

• Eight eMudhra intermediate CA certificates have compromised private keys.
• The flaw originated in April 2025 during incorrect key generation by the CA.
• Private keys were recoverable from the public certificates, not stolen via hack.
• Mozilla, Apple, and Chrome blocked the certificates between October 17 and 19, 2026.
• Clients outside the browser ecosystem may still trust these intermediates until updated.
• No Certificate Transparency logs exist for these intermediates, limiting historical visibility.

Background

To understand the severity, it helps to know how digital trust works. When you visit a secure website, your browser checks the site's TLS certificate. This certificate is signed by an intermediate CA, which is in turn signed by a root CA. Your device trusts the root CA, and by extension, trusts the intermediate and the website. If an attacker has the private key of an intermediate CA, they can create valid certificates for any domain, such as your bank or email provider. This allows them to intercept encrypted traffic without triggering security warnings.

Certificate Transparency (CT) is a system that logs all issued certificates in public ledgers. Browsers like Chrome and Safari require CT logs to accept certificates. In this case, there were no CT log entries for these specific intermediates during the vulnerable period. This means that while browsers were protected from seeing fraudulent certificates issued after the fact, the underlying key weakness remained. Systems that do not enforce CT, such as many command-line tools, embedded devices, and legacy enterprise software, remain at risk if they have not received updates to distrust these specific intermediates.

Why it matters

For teams running self-hosted software or managing internal infrastructure, this incident highlights a blind spot in standard security monitoring. Most organizations rely on operating system and browser updates to handle trust store changes. However, custom applications, microservices, and IoT devices often maintain their own trust stores or use lightweight TLS libraries that do not automatically sync with OS-level revocation lists. If your internal services communicate with external APIs or if you host services for clients using diverse clients, those connections may still trust the compromised eMudhra intermediates.

The fact that the keys were recoverable from public data is particularly alarming. It suggests that the security failure was procedural and mathematical, not just operational. This means that similar errors could exist in other CAs or past certificates. For IT leads, this reinforces the need to verify not just that your certificates are valid, but that the chain of trust itself is intact and free from known compromised authorities. Relying solely on automatic browser updates leaves gaps in non-web-facing infrastructure.

What you can do

• Update all browsers and operating systems to the latest versions immediately to ensure revoked certificates are blocked.
• Test command-line tools like curl against the verification hosts listed in the disclosure to check local trust stores.
• Review any custom applications or embedded devices that use static trust stores for outdated intermediate certificates.
• Verify that your monitoring systems alert on certificate changes, not just expiry dates.
• Check if your organization uses eMudhra certificates internally and replace them if they chain to the affected intermediates.
• Monitor official updates from Mozilla, Apple, and Microsoft for further guidance on downstream trust store patches.