eMudhra Intermediate CA Keys Compromised: What Happened

CERT-In said eMudhra reported that private keys for eight intermediate CA certificates had been compromised, in an advisory issued on 21 October 2026.

By Career Ahead AI — AI-assisted, fact-verified against cited sources. Readers should verify key facts.

Weak randomness made the intermediate keys recoverable

The advisory, CIAD-2026-0050, concerns eMudhra Limited’s public key infrastructure (PKI). The affected certificates were intermediate certification authorities, which sit between a root certificate authority and certificates issued for individual services. CERT-In said the private keys associated with these intermediates had been compromised.¹²³⁴⁵

The keys were generated with insufficient cryptographic randomness. Mozilla’s incident report said the affected certificates used P-384 elliptic-curve keys generated in April 2025, with values smaller than 256 that could be recovered by testing 256 possible numbers. CERT-In said the keys’ exceptionally small values made them potentially recoverable almost instantly. It warned that attackers could use them to intercept or modify communications and potentially expose sensitive information, including financial data.¹²³⁵

The keys were generated with insufficient cryptographic randomness.

A security researcher known as Wayne discovered the weakness while scanning publicly available certificate data. eMudhra attributed it to an error in a certificate-generation script that produced a second set of weaker keys; similar labels led those keys to be selected for certificate signing. Some resulting certificates were submitted to Sectigo for cross-signing. Researcher Flüpke demonstrated the flaw by publishing a compromised private key for the “EM OV TLS CA – G3C” certificate, whose value was 4.¹²³⁴

eMudhra said none of the affected intermediate CAs had issued end-entity certificates. It also said most affected intermediates were never used in production and that it found no evidence they had issued certificates to end users. After disclosure, the company revoked the compromised certificates and stopped issuing new certificates under its G3 root.¹²³⁴⁵

Browser vendors blocked the affected certificates

On October 17, 2026, the Chrome Root Program received a researcher’s report at 18:05 UTC. Chrome completed its checks and landed a CRLSet update at 19:45 UTC, blocking the public keys of the affected TLS intermediates. Chrome and Firefox blocked the affected certificates that day. Mozilla blocked six TLS intermediate certificates through its OneCRL block list and released Firefox 158.0.1 for desktop and Android, Firefox ESR 115.45.1 and Firefox ESR 153.5.1.¹²³⁴⁵

Android devices and Googlebooks received an equivalent update through Google Play Services around 22:00 UTC on Monday. Google said no TLS certificates chaining to the affected intermediates had appeared in Certificate Transparency logs before its blocking action, so fraudulent certificates issued by them could not have been used against clients that enforce those logs. Google scheduled the removal of emSign ECC Root CA – G3 from the Chrome Root Store for Tuesday morning, 27 October 2026 PDT, with an earlier release on prerelease channels.¹²³⁴⁵

The Go development team released versions 1.27.3 and 1.26.10 to address the issue, tracked as CVE-2026-111943. Google also said it reviewed its root stores and confirmed that no other included keys shared the same weak-entropy failure mode.²³

Cloudflare reported mitigations and no active exploitation on its services

Apple added protections on October 19, and Cloudflare said it became aware of the compromised keys at approximately 17:00 UTC that day. Microsoft followed on October 20. Cloudflare said its security review had not identified active exploitation on its services. It released updates for Cloudflare One Clients, also known as WARP or the 1.1.1.1 app, and Cloudflare Tunnel, also known as cloudflared, and deployed mitigations across its CDN, Developer and Zero Trust products.¹²³⁴⁵

The Go development team released versions 1.27.3 and 1.26.10 to address the issue, tracked as CVE-2026-111943.

Prioritise PKI Key Assurance

If you are choosing a security course or role, weigh work involving PKI, certificate generation or CA operations, and build the skill of checking how private-key randomness is generated and tested. eMudhra traced the weak keys to an error in a certificate-generation script, and the P-384 keys’ exceptionally small values made them potentially recoverable almost instantly. Script review and key-generation assurance are concrete topics to test in a course or portfolio project, rather than treating cryptography as theory alone.¹²³⁴

When comparing employers or preparing for interviews, ask who owns certificate incident response, how affected certificates are identified and revoked, and how protections reach users. eMudhra revoked the compromised certificates and stopped issuing new certificates under its G3 root; browser vendors blocked affected certificates, and Google delivered an equivalent update to Android devices and Googlebooks. Those details help you assess whether a role includes practical certificate lifecycle and response work, not just security monitoring.¹²³⁴⁵