In brief
Eight intermediate certificate authority keys belonging to eMudhra, an Indian certificate authority, turned out to be so weak that anyone could calculate them from public information. Browsers blocked them within hours of being told. No misuse has been confirmed. But the incident cost eMudhra its place in the web's trust system for website certificates, and it holds lessons for every security team.
What happened?
On the evening of October 17, 2026, a security researcher reported to Google, Mozilla, Apple and Microsoft that the private keys for eight eMudhra intermediate certificates could be recovered. Google's Chrome Root Program received the report at 18:05 UTC.
A certificate authority vouches for websites. When your browser shows a padlock, a chain of certificates says this really is your bank. An intermediate key sits in that chain, so whoever holds it can sign certificates browsers believe. Google says these keys were generated with insufficient randomness, letting anyone forge trusted certificates for any website against software that still trusted them.
How weak? Researcher Scott Helme told The Register that one key is the number 4. A properly made key is a random number hundreds of digits long.
Chrome confirmed the finding and blocked the keys by 19:45 UTC. Mozilla protected Firefox users in less than 3 hours. Google later removed the eMudhra root that signed them from the Chrome Root Store, and Mozilla did the same for its trust list.
How it happened, according to eMudhra
eMudhra has published a running statement. Its account:
- The eight intermediates were created in a key ceremony on April 30, 2025, on certified hardware security modules.
- During that ceremony, a key wrap/unwrap step produced a second, weak set of keys, and the weak set is what was published to browsers.
- The problem went undetected for about 18 months, through two independent audit cycles.
- In a note from its leadership, the company wrote plainly: the flaw was ours, caused by a script error.
It says a full root-cause analysis will follow, and it has appointed KPMG as an independent external reviewer.
What is confirmed?
- The keys were generated with insufficient randomness and could be computed by anyone (Google).
- Major browsers blocked them within hours (Google, Mozilla).
- No fraudulent certificate from these keys could have been used against browsers that enforce Certificate Transparency, which includes Chrome by default (Google).
- eMudhra says seven of the eight were never used in production, and the eighth issued no certificates (eMudhra).
What was not affected
Early reactions online suggested every certificate eMudhra had ever issued was now untrustworthy. The official accounts are narrower. eMudhra says its digital signature certificate and eSign business is not affected, and those run on separate infrastructure. The disruption falls on website certificates under the removed root: eMudhra says roughly 30,800 such certificates belong to one client ecosystem in the United States, which it is moving to other providers.
What remains unknown?
- The full root cause. eMudhra has said its analysis is still to come.
- Whether anyone found the keys before October 17. eMudhra says it is not aware of evidence that they did. Over 18 months, that is hard to prove either way.
- The future of eMudhra's other certificates. Google says it is closely investigating their continued inclusion.
Why it matters
India's digital economy leans heavily on certificate authorities, and this is one of the country's best known. The company is also stepping back: it says it is winding down its publicly trusted website certificate business.
Our reading of the lessons:
Strong hardware didn't save a weak process. The keys were made on certified modules. One step in the procedure still produced bad keys. Security lives in the whole process, not the box.
Audits checked, but didn't catch it. Two audit cycles passed. An audit confirms you followed your procedures. It doesn't always test whether the output is sound.
Fast ecosystem response limited the damage. Certificate Transparency logging and browser blocklists meant a serious flaw was contained within hours.
What readers should do
- Everyday users: update your browser and phone. Major browsers have already blocked these keys.
- If you ran a website with an eMudhra certificate: check whether it chains to emSign ECC Root CA - G3, and replace it if so.
- Developers and IT teams: software that bundles its own list of trusted certificates may still trust the removed root. Update those packages and trust stores.
- Security leaders: ask your own suppliers how their key generation is verified, not just whether it was audited.
Right of reply
eMudhra has published a detailed, regularly updated statement on this incident, which we cite throughout. We have not yet put separate questions to the company. If eMudhra responds or publishes its full root-cause analysis, we will update this story.
Sources
- Protecting Chrome and Android users from compromised eMudhra intermediate CA certificates (Google, October 20, 2026)
- Protecting Firefox users following the compromise of eMudhra intermediate certificates (Mozilla, October 20, 2026)
- eMudhra statement on recent certificate security incident (eMudhra, updated October 30, 2026)
- Indian certification authority eMudhra's private keys compromised (The Register, October 20, 2026)