Browser makers, along with some major apps and programming languages, had blocked all eight compromised intermediate certificates as of late morning Tuesday, Ars Technica reported on October 20, 2026. There were no reports of suspicious certificate transparency log entries at the time of writing.
The eight intermediate certificates belong to eMudhra Limited, a certificate authority based in India. An informal advisory posted to emudhra.we-have-a-problem.com carried the message 'We have a problem here - Wayne,' digitally signed in a way that confirmed the poster held the compromised private keys.
An intermediate CA certificate with a leaked private key is a worst-case supply-chain event for the web's trust model: anyone holding the key could mint browser-trusted certificates for arbitrary domains until the intermediates are blocked, enabling interception that shows no visible warning.
Blocking the intermediates severs that path, but it also invalidates every legitimate site certificate chained to them, which is why CA compromises cause collateral outages even when handled quickly. Site operators who bought certificates through eMudhra should confirm with the CA whether their chain is affected and plan reissuance.
The open question is how the keys escaped. Whether the compromise was an outside intrusion, an insider act or an operational mistake has not been established, and the answer will shape whether eMudhra retains its place in browser root programs.