eMudhra Has Quit TLS. The Accountability Questions Haven’t

Removing a root certificate from Chrome’s trusted list withdraws the browser’s automatic trust in certificates connected to that root. For affected websites, this can turn a normal visit into a prominent security warning. The change followed the discovery that eight private keys under eMudhra’s global hierarchy were dangerously weak.

Chrome had already blocked six website-securing certificates through CRLSet on October 17. CRLSet lets Google send a blocklist to browsers without requiring a browser update or restart. On October 27, Chrome removed emSign ECC Root CA–G3 from the Chrome Root Store, a stronger action than blocking individual certificates.

The immediate effect was visible to Chrome users visiting websites that still depended on the removed root. Google also said no certificates from the six affected intermediates appeared in public Certificate Transparency logs before the block. eMudhra revoked the certificates, while Google investigated whether its remaining roots should stay trusted.

A TLS certificate helps a browser check that a website is presenting a valid digital identity. It links the website’s domain name with a public key and is digitally signed by a certificate authority, or CA. TLS also protects data exchanged between the browser and website, such as passwords or payment details.

When a browser connects, it checks the certificate’s name, validity period, signature, and trust chain. The chain normally ends at a root certificate already included in the browser or operating system’s trusted store. If the chain is broken, revoked, expired, or signed by an untrusted root, the browser can display a security warning.

The article shows why this system matters. Once browsers blocked eMudhra’s affected certificates and removed emSign ECC Root CA–G3, websites relying on that chain stopped receiving automatic trust. Chrome said no affected certificates appeared in public Certificate Transparency logs before blocking.

Eight private keys belonging to certificate authorities under eMudhra’s global hierarchy were found to be weak. Private keys are supposed to be difficult to derive or guess. They protect a certificate authority’s ability to sign digital certificates, so weak keys can undermine trust far beyond one website.

The article gives a striking example: one private key was the number 4. Each key should have been about 116 digits long, but all eight were below 256. The researcher said anyone could work them out. The weak keys were created during one key ceremony on April 30, 2025, after a flaw produced a second, weak set of keys.

The problem went unnoticed for about 18 months and across two audit cycles. After the report on October 17, browsers blocked the affected certificates, software maintainers issued emergency patches, and eMudhra revoked the certificates. Its board then decided to leave the global TLS certificate business.

Browsers reacted quickly because certificate authorities sit inside the web’s trust system. If an attacker can derive a CA’s private key, they may be able to create certificates that appear legitimate. That could let software accept a false identity for a website or service. The article reports that eMudhra’s eight weak keys were potentially calculable by anyone.

Google received the researcher’s report on October 17 and reacted within one hour and 40 minutes. Chrome blocked six certificates through CRLSet. Firefox moved within hours, while Apple patched Safari on October 19 and Microsoft patched Edge and older browsers on October 20. Mozilla and Chrome then removed the affected root from their trusted stores.

The speed reflected the seriousness of the trust failure, not evidence that the certificates had been abused. Chrome said none of the six intermediates appeared in public Certificate Transparency logs before its block. eMudhra revoked the certificates, and its board chose to exit global TLS certificates.

A certificate authority, or CA, is a trusted organisation that issues digital certificates. Those certificates connect a website or organisation with a cryptographic key and help browsers verify identity. CAs therefore act as important trust anchors for secure web connections. The article identifies eMudhra as India’s largest licensed certifying authority.

When a browser receives a website certificate, it checks whether a trusted CA signed it or whether the certificate leads through intermediates to a trusted root. Browsers and operating systems store approved root certificates in advance. Removing a root means certificates tied to it are no longer automatically accepted by the relevant software.

That is what happened to eMudhra’s emSign ECC Root CA–G3. Mozilla removed it from its trusted list, and Chrome removed it from the Chrome Root Store effective October 27. Apple and Microsoft also issued patches. In India, the Controller of Certifying Authorities regulates and permits CAs to issue digital signature certificates.

The key-generation mistake happened during a formal key ceremony on April 30, 2025. eMudhra said a flaw in its ceremony script created a second, weak set of keys. Those keys were used by mistake because their labels looked similar to the labels for the intended keys. The result was eight private keys far shorter than required.

Industry rules require key ceremonies to follow a written script. A qualified auditor must watch the process or it must be recorded on video. The ceremony must also be signed off in an auditor’s report. These controls are designed to catch process failures and prove that key generation followed the approved procedure.

Yet the flaw went undetected for about 18 months and across two audit cycles. eMudhra cofounder Kaushik Srinivasan called it “a one-off, a bad day” and said he did not know how it escaped review. An auditor’s report was due two to three weeks after the incident, while browser makers had already blocked the certificates.

The article identifies India’s Controller of Certifying Authorities, or CCA, as the regulator that permits and oversees certificate authorities such as eMudhra. It also says the IT ministry, MeitY, formed a special team to investigate the incident. CERT-In issued an advisory four days after the initial vulnerability report.

The possible accountability issue concerns the required controls around key ceremonies and audits. Industry rules require a written ceremony script, qualified observation or video recording, and an auditor’s report. The article says eMudhra’s weak keys were created during one ceremony and remained undetected through two audit cycles. An auditor’s report was still due two to three weeks after the incident.

The article does not state which specific rule was formally found to be broken, nor does it give a penalty or fine. It leaves those questions open while the situation develops. eMudhra revoked the certificates and decided to exit the global TLS certificate business, which it said contributed 1% of revenue.