Tsaaro got CERT-IN Empanelled | MeitY has published the DPDP Rules, 2023.
Tsaaro got CERT-IN Empanelled | MeitY has published the DPDP Rules, 2023.
Tsaaro got CERT-IN Empanelled | MeitY has published the DPDP Rules, 2023.
Tsaaro got CERT-IN Empanelled | MeitY has published the DPDP Rules, 2023.
Back To Home
Data privacy

Introduction
A recent certificate-security incident involving eMudhra has drawn attention to a less visible layer of internet security: the infrastructure browsers rely on to decide whether a website can be trusted. On 21 October 2026, CERT-In issued an advisory concerning eight eMudhra intermediate Certificate Authority (CA) certificates whose private keys had been generated with a serious cryptographic weakness. The incident was widely reported on 23 October because those keys could potentially have been used to create fraudulent certificates for websites an attacker did not control.
The incident did not amount to a compromise of eMudhra’s entire infrastructure. eMudhra states that the eight affected intermediate certificates were revoked on 18 October, that none had issued publicly trusted end-entity certificates, and that its Indian Digital Signature Certificate (DSC) and eSign infrastructure was separately operated and unaffected. The episode still raises an important question about digital trust: what happens when the credentials used to prove that websites are genuine can themselves no longer be trusted?
What Happened at eMudhra?
eMudhra operates in two relevant areas. In India, it is a licensed Certifying Authority providing digital-signature and eSign services under the framework supervised by the Controller of Certifying Authorities (CCA). Separately, its international public-trust business issues certificates used by browsers and operating systems to establish secure connections to websites and other online services.
The incident concerned the second business. According to CERT-In and eMudhra, eight intermediate CA certificates created during an April 2025 key-generation ceremony had unusually weak private keys. CERT-In states that the affected P-384 elliptic-curve keys had values small enough to be recovered from their corresponding public keys. The weakness arose during the key-generation process rather than from a flaw in the P-384 cryptographic algorithm itself.
eMudhra later explained that an error during a wrap-and-unwrap step in the key-generation ceremony produced weak keys alongside the intended strong ones, and the weak keys were ultimately published to browser root programmes. The company acknowledged responsibility for the process failure and began reviewing its key-generation procedures.
Why Does a Compromised CA Key Matter?
HTTPS depends on digital certificates to help establish that a user is communicating with the website they intended to visit. Browsers rely on trusted Certificate Authorities to issue these certificates, forming what is commonly called the Web Public Key Infrastructure, or WebPKI.
An intermediate CA occupies an important position within that trust chain. If its private key can be recovered, an attacker may potentially create certificates that appear to have been validly issued by a trusted authority. CERT-In warned that such certificates could be used to impersonate legitimate websites or support man-in-the-middle attacks where an attacker is also able to intercept the user’s network traffic.
The resulting risk can extend beyond a misleading imitation webpage. A fraudulent TLS certificate may allow an attacker in the necessary network position to make an impersonated service appear cryptographically genuine, creating opportunities to intercept or modify information that users believe is travelling over a secure connection.
CERT-In also noted that compromised code-signing keys could create a related problem by allowing malicious software to appear as though it had been signed by a trusted publisher. The incident shows why CA security is treated differently from the compromise of an ordinary website account: weakness at a trust-provider level can potentially affect systems far beyond the organisation itself.
Browser Operators Moved Quickly
Mozilla was notified of the affected keys on 17 October and blocked the relevant certificates in Firefox through OneCRL, its centralised certificate-blocking mechanism. Mozilla stated that the change had been distributed to standard Firefox installations in less than three hours. It subsequently released updates for Firefox and Firefox ESR to protect configurations that might not receive OneCRL changes normally.
Mozilla also removed the emSign ECC Root CA - G3 certificate associated with the affected hierarchy from its Network Security Services trusted-certificate list. This broader measure addressed applications that rely on Mozilla’s trust store but may not receive certificate-revocation information through Firefox itself.
Google similarly blocked the affected TLS intermediate public keys through Chrome’s CRLSet mechanism and extended protections to supported Android devices through Google Play services. CERT-In reported that Google also decided to remove the relevant root from the Chrome Root Store. Chrome’s own Root Program Policy explains why this matters: certificates chaining to authorities that Chrome no longer trusts may trigger warnings or be rejected instead of being treated as valid proof of a secure connection.
Was There Evidence of Actual Website Impersonation?
CERT-In stated that, as of 21 October, public disclosures had not established confirmed malicious exploitation of the affected keys. Google also reported that no TLS certificates chaining to the six affected TLS intermediates had appeared in Certificate Transparency logs before its blocking action. eMudhra maintains that the affected intermediate CAs had not issued any end-entity certificates.
The incident created the capability for certificates to be forged, but that is different from evidence that fraudulent certificates were actually issued and used against users. The rapid revocation and browser-side blocking substantially reduced the window in which the affected hierarchy could be relied upon.
There can still be operational consequences after such an event. Removing trust in a root certificate can cause otherwise legitimate certificates that depend on that hierarchy to stop working on affected devices. eMudhra has since said that it is helping customers move to alternative publicly trusted certificates and offering CA redundancy to reduce dependence on a single hierarchy.
Indian DSC and eSign Services Were Separate
The distinction between eMudhra’s international WebPKI operation and its Indian regulated services became particularly important as reports of the incident spread.
CERT-In expressly stated that its advisory concerned eMudhra’s browser- and operating-system-trusted certificate business. The company’s Digital Signature Certificate and eSign services regulated by the CCA under MeitY were not affected. According to the advisory, the domestic infrastructure uses separate cryptographic keys and operates under a distinct regulatory framework.
The CCA continues to list eMudhra as a licensed Certifying Authority and an empanelled eSign provider. This separation is important because a certificate used to establish an HTTPS website connection and a DSC used to authenticate an electronic document perform different functions even though both depend on public-key cryptography.
Treating the incident as a compromise of all eMudhra digital-signature services would consequently overstate its scope. The affected hierarchy belonged to the international public-trust certificate environment, while the domestic DSC and eSign infrastructure remained architecturally separate.
The Incident Exposes a Governance Problem as Much as a Cryptographic One
The immediate flaw arose during key generation, but the wider issue concerns the governance around creating and validating highly trusted cryptographic credentials.
eMudhra states that the affected keys were generated using FIPS 140-2 Level 3 certified Hardware Security Modules. The presence of certified hardware did not prevent a procedural or scripting failure from producing insecure keys. This illustrates the limits of treating compliance with a technical standard as proof that the entire certificate lifecycle is secure.
For Certificate Authorities, controls around key-generation ceremonies, independent verification and post-generation validation are especially important because errors may become embedded in the trust infrastructure used by browsers and applications. eMudhra has since appointed an independent external reviewer, begun reviewing its key-generation procedures and announced measures intended to provide additional certificate redundancy for customers.
The incident also demonstrates the value of transparency within the WebPKI ecosystem. An independent researcher identified the problem, browser operators were informed, affected certificates were rapidly blocked and the CA publicly documented its response. That chain of detection and coordinated mitigation prevented a cryptographic weakness from remaining silently trusted for longer.
What Should Organisations Do?
Organisations relying on public-trust certificates should review how certificate security fits within their wider cybersecurity processes:
Map certificate dependencies: Identify which root and intermediate certificates critical websites, applications and services depend on.
Plan for rapid replacement: Maintain procedures for replacing certificates quickly if a Certificate Authority or trust hierarchy is revoked or distrusted.
Keep systems updated: Ensure browsers, operating systems, applications and security libraries receive current trust-store and revocation updates.
Check embedded certificate stores: Applications and SDKs that maintain their own trust stores may need separate remediation rather than inheriting browser or operating-system updates automatically.
Review third-party CA risk: Organisations should understand how their certificate providers manage key generation, incident response, revocation and continuity arrangements.
Strengthen key-generation controls: Certificate Authorities and trust-service providers should use independent checks capable of detecting anomalous keys before they enter trusted infrastructure.
Validate beyond hardware certification: A successful operation inside a certified Hardware Security Module should not replace independent verification that the resulting key is cryptographically sound.
Conclusion
The eMudhra incident did not produce evidence of a widespread compromise of Indian websites, nor did it affect the company’s domestic DSC and eSign infrastructure. Its significance lies in what could have happened if weak intermediate CA keys had remained trusted and had been misused.
CERT-In’s warning illustrates how website security depends on a chain of trust extending well beyond the website itself. When an intermediate CA key becomes unreliable, browsers, certificate authorities, software vendors and website operators all have a role in containing the resulting risk.
The rapid response by Mozilla, Google, CERT-In and eMudhra substantially limited the exposure in this case. The broader lesson is that digital trust depends as much on strong key-generation governance, rapid revocation and coordinated trust-store updates as it does on the cryptographic algorithms underlying the certificates.
Want to Stay Ahead?
Reach out to the experts at Tsaaro today.
Talk to a Privacy Expert
Get a free 1:1 session on AI compliance, DPDPA readiness, or incident response planning.
Related articles













