eMudhra CA keys compromised by weak randomness flaw
Eight eMudhra intermediate CA certificates were revoked after a key generation flaw made their private keys easily computable, triggering emergency blocks across Chrome, Firefox, and Go.

Eight eMudhra intermediate certificate authority certificates are compromised because their private keys were generated with insufficient randomness. Mozilla and Google's Chrome Root Program confirmed the compromise on October 20, leading to immediate browser blocks. The flaw made the keys computationally derivable from their public certificates, meaning they did not need to be stolen.
A researcher, credited only as Wayne, reported the compromise to browser root programs on the evening of October 17. To prove control, he signed a message with each of the eight private keys. The message read, "We have a problem here - Wayne." Chrome and Firefox verified the findings and blocked the certificates within hours. Chrome pushed a CRLSet update by 19:45 UTC, and Mozilla distributed a OneCRL block to Firefox by 22:59 UTC that same day.
Apple blocked the certificates on October 19, with Microsoft following on October 20. Android devices received a block via Google Play Services around 22:00 UTC on October 19. eMudhra has revoked all eight certificates. Mozilla stated that, for now, the problem does not appear to affect other certificate authorities. Chrome said it checked every other CA in its store and found no other instances of this failure mode.
The nature of the flaw
The private keys were generated with too little entropy, making them trivial to compute from the public certificates. eMudhra stated on October 21 that a flaw in an April 2025 key generation ceremony produced a second, weak set of keys alongside the intended strong ones. The weak set was mistakenly published to browser root stores.
Security researcher Scott Helme demonstrated the severity by recovering all eight private keys from the public certificates on his laptop in under a second. He noted that one key is simply the number 4, and the rest are whole numbers below 256. eMudhra emphasized its infrastructure was not breached and that its roots had passed independent audits for two consecutive years.
Browser and platform actions
Major browsers and operating systems moved swiftly to block the compromised certificates and update their trust stores. Chrome's block targets the public key, which also catches cross-signed copies of the certificates from Sectigo. Both Chrome and Mozilla stated that no public TLS server certificates had been issued under the affected intermediates prior to the block, aside from internal test certificates.
Mozilla released patched versions of Firefox for users unable to receive the OneCRL update. The organization also removed the emSign ECC Root CA - G3 from its NSS library. Chrome will remove the same root in version 43 of its Chrome Root Store, expected to propagate on the morning of October 27, Pacific Time. Chrome is evaluating the trust status of eMudhra's remaining certificates.
Impact on software and developers
The vulnerability significantly impacts software relying on the Go programming language and other runtimes, requiring updates and rebuilds. Go released patched versions 1.27.3 and 1.26.10 with a fix tracked as CVE-2026-111943. The release notes were kept deliberately vague because the flaw was easy to exploit and expected to become public.
Filippo Valsorda, who maintains Go's cryptography packages, explained that embedding the compromised key hashes in code is the only reliable option for now. This is because Linux root stores are often too poorly maintained for standard revocation to reach applications. Go's verifier does not perform revocation checks, so a revoked intermediate remains trusted until a new release ships. The fix adds a filter that hashes each certificate's public key, which also catches cross-certificates sharing the same compromised keys.
The eight compromised intermediate certificates are:
| Certificate Type | Validation Level | CA Version |
|---|---|---|
| TLS | Domain Validated (DV) | G3B |
| TLS | Domain Validated (DV) | G3C |
| TLS | Organization Validated (OV) | G3B |
| TLS | Organization Validated (OV) | G3C |
| TLS | Extended Validation (EV) | G3B |
| TLS | Extended Validation (EV) | G3C |
| Code Signing | Organization Validated (OV) | G3B |
| Code Signing | Organization Validated (OV) | G3C |
Developers must move to the patched Go releases, then rebuild and redeploy affected binaries. Go versions 1.25 and older are out of support and will not receive fixes. Projects like Bluesky and the gRPC health probe have already rebuilt with the new releases.
Ongoing status and unknowns
The full extent of the risk and the long-term trust status of eMudhra remain under evaluation. There is no known way to detect past misuse of the keys beyond searching Certificate Transparency logs, which only cover logged certificates. Mozilla warned that network interceptors could have used fraudulent certificates to impersonate trusted sites and read or alter user data.
Roland Shoemaker of the Go security team wrote that the team learned of the underlying problem on October 19. eMudhra's shares fell 20% in Mumbai trading on October 21. The company, an Indian CA that sells certificates under the emSign brand, had issued more than 60 million certificates. Trust store operators who cannot block individual intermediates are advised to consider removing trust in the eMudhra roots that signed the compromised certificates. Systems must update to the patched Go versions, and browser root stores are actively removing trust in the compromised eMudhra roots.





