Act this weekWhat happenedMozilla and Google confirmed on October 20 that the private keys of eight eMudhra intermediate certificates are compromised.
Who is affectedAnyone using web browsers or software that trusts eMudhra certificates, including Chrome, Firefox and other tools that rely on them.
What to do- 1Install the latest browser updates on every work computer and phone.
- 2Apply pending updates to operating systems and business software.
- 3Ask your IT provider whether any of your tools use eMudhra certificates.
- 4Warn staff to be careful with login and payment pages until updates are done.
Mozilla and Google's Chrome Root Program confirmed on October 20 that the private keys for eight certificates from eMudhra, an Indian certificate company, are compromised. Chrome and Firefox blocked the certificates within hours of a researcher's report. The bigger worry is other software that does not get blocks pushed to it the way browsers do.
What happened
A certificate authority is a company that vouches that a website is genuine. An intermediate one signs the certificates that websites show your browser. Anyone holding one of these eight keys could issue a certificate for any website that a browser would accept. That is how a fake bank or login page could look safe.
The keys were not stolen in the usual sense. They were made with too little randomness, so anyone can work them out from the public certificates. eMudhra said a flaw in the April 2025 ceremony that created the certificates produced a second, weak set of keys. Researchers have since published the keys.
Who can relax
Browser users are in good shape. Chrome and Firefox fetch block lists on their own, so neither needed an update or a restart. Apple blocked the certificates on October 19 and Microsoft on October 20. Android got a block through Google Play Services on October 19. Chrome also said no website certificate from the six website-related intermediates had been logged publicly before its block, so none could have been trusted by default.
Mozilla does not believe, for now, that other certificate companies are affected. Chrome said it checked every other one in its store and found no other cases.
Who should check
Many programs that check website certificates do not look at block lists. They keep trusting a certificate until their code or their bundle of trusted companies changes. The material names programs built with Go and tools using Python's certifi bundle as examples. Go released a fix on October 20, but a program only gets it when it is rebuilt. Go 1.25 and older get no fixes.
Some fixes work by removing whole trusted companies from software lists. That also cuts off legitimate sites that rely on them, so some servers may become unreachable for some tools.
What to do
The steps in the alert box above cover the practical side. In short, update browsers and business software, and ask your IT provider whether any of your tools rely on eMudhra certificates.
What is not known
Whether anyone used the flaw since the certificates were created in April 2025 is not known. Go treated its fix as urgent, but neither its issue nor its release notes say whether that was for ecosystem safety or for attacks already happening.
The takeawayBrowsers already blocked the eight certificates, so update them anyway and ask your IT provider about other software that may still trust eMudhra.