44
eMudhra has decided to withdraw from its global SSL/TLS certificate business after a cryptographic key-generation flaw compromised the security of eight intermediate certificate authorities, prompting major browser providers to restrict trust in the affected certificate hierarchy. The
incident raised concerns about the reliability of internet security infrastructure. However, the company said it found no evidence of an infrastructure compromise or customer data breach.
The Bengaluru-based digital trust company announced its board’s decision on October 22, 2026, following the disclosure of the security incident. The global SSL/TLS business contributes approximately 1% of eMudhra’s global revenue, according to the company. It said it would focus on its core enterprise solutions and other digital trust services while supporting customers through the transition.
The incident emerged on October 17, when an independent security researcher reported that private keys associated with eight eMudhra intermediate certificate authorities could be recovered. The company revoked all eight intermediate authorities on October 18, stating that it had acted within 14 hours of confirming the issue.
In an update published on October 26, eMudhra attributed the weakness to a scripting error during a cryptographic key-generation procedure. The company apologised to customers and the wider web security community, committed to an independent expert review and said it would publish a detailed root-cause analysis through the Common Certificate Authority Database process. The weakness originated during a key-generation ceremony on April 30, 2025. According to eMudhra, an error in a wrap-and-unwrap step generated a second set of weak keys alongside the intended strong keys. These weak keys were subsequently included in browser trust stores. The company acknowledged that the issue went undetected through two independent audit cycles and said its investigation into the precise root cause was continuing.
India’s Computer Emergency Response Team (CERT-In) said the affected P-384 elliptic-curve private keys had been generated with insufficient cryptographic randomness. As a result, the private keys could reportedly be recovered almost instantly from their corresponding public keys. The weakness arose from the key-generation process rather than a vulnerability in the P-384 algorithm itself.
Certificate authorities issue digital certificates that browsers and operating systems use to verify website identities and establish secure connections. If an attacker obtains an issuing authority’s private key, they may be able to create fraudulent certificates for domains they do not control. Depending on the affected trust chain and the circumstances of an attack, such certificates could enable website impersonation and the interception or modification of communications. If affected code-signing keys are involved, they could also be misused to issue fraudulent signing certificates. According to eMudhra, none of the eight affected intermediate authorities had issued end-entity certificates. Seven had never been used in production, while the eighth had been deployed but had not issued any certificates. The company said it had no evidence that the weak keys had been recovered or exploited before disclosure.
These findings are important in distinguishing the seriousness of the cryptographic flaw from evidence of actual exploitation. Although the weakness created a potential security risk, the company has not reported confirmed malicious use of the affected keys.
Browser providers responded with measures to block the affected certificates and reduce the risk to users. Apple began blocking the affected intermediate certificates on October 19 and said its devices automatically receive the relevant protections. Mozilla blocked the affected certificates in Firefox and issued additional updates for users whose configurations might prevent them from receiving the protections. Google implemented blocking measures in Chrome and supported Android devices and announced the removal of the emSign ECC Root CA – G3 from the Chrome Root Store.
The removal of the root certificate could have wider implications than the revocation of the eight intermediate authorities alone. Some otherwise legitimate certificates that chain to the affected root may no longer be trusted by systems that remove it from their trust stores. Google said the Chrome Root Store change was expected to reach relevant devices on October 27, 2026. The precise impact depends on the browser, operating system, application and certificate chain involved.
eMudhra said its Indian digital-signature and eSign services, along with its enterprise applications, operate on separate infrastructure and were not affected. The company is arranging replacement certificates for affected customers at no cost and has offered certificates issued by Sectigo as an alternative. It also said its G1 RSA root certificates would continue to serve customers while the transition away from the global SSL/TLS business is completed.
For organisations using certificates associated with the affected hierarchy, the immediate priority is to identify potential dependencies, obtain replacement certificates where necessary and verify that websites and applications continue to function across browsers and devices. Administrators should also review systems that maintain independent certificate trust stores, as they may not receive the same protections automatically.
The incident raises broader questions about cryptographic implementation, operational oversight and the effectiveness of security audits. The failure to detect weak keys across two independent audit cycles highlights the importance of testing not only the intended cryptographic algorithms but also the procedures used to generate and manage their keys.
It also demonstrates how a technical error within a single certificate authority can trigger a coordinated response across the internet’s trust infrastructure, requiring action from browser providers, businesses and system administrators.
The eMudhra case underscores a fundamental principle of cybersecurity:trusted digital identities depend not only on strong cryptographic algorithms but also on correctly implemented key-generation procedures, rigorous testing and a coordinated response when vulnerabilities are discovered.
The Bengaluru-based digital trust company announced its board’s decision on October 22, 2026, following the disclosure of the security incident. The global SSL/TLS business contributes approximately 1% of eMudhra’s global revenue, according to the company. It said it would focus on its core enterprise solutions and other digital trust services while supporting customers through the transition.
The incident emerged on October 17, when an independent security researcher reported that private keys associated with eight eMudhra intermediate certificate authorities could be recovered. The company revoked all eight intermediate authorities on October 18, stating that it had acted within 14 hours of confirming the issue.
In an update published on October 26, eMudhra attributed the weakness to a scripting error during a cryptographic key-generation procedure. The company apologised to customers and the wider web security community, committed to an independent expert review and said it would publish a detailed root-cause analysis through the Common Certificate Authority Database process. The weakness originated during a key-generation ceremony on April 30, 2025. According to eMudhra, an error in a wrap-and-unwrap step generated a second set of weak keys alongside the intended strong keys. These weak keys were subsequently included in browser trust stores. The company acknowledged that the issue went undetected through two independent audit cycles and said its investigation into the precise root cause was continuing.
India’s Computer Emergency Response Team (CERT-In) said the affected P-384 elliptic-curve private keys had been generated with insufficient cryptographic randomness. As a result, the private keys could reportedly be recovered almost instantly from their corresponding public keys. The weakness arose from the key-generation process rather than a vulnerability in the P-384 algorithm itself.
Certificate authorities issue digital certificates that browsers and operating systems use to verify website identities and establish secure connections. If an attacker obtains an issuing authority’s private key, they may be able to create fraudulent certificates for domains they do not control. Depending on the affected trust chain and the circumstances of an attack, such certificates could enable website impersonation and the interception or modification of communications. If affected code-signing keys are involved, they could also be misused to issue fraudulent signing certificates. According to eMudhra, none of the eight affected intermediate authorities had issued end-entity certificates. Seven had never been used in production, while the eighth had been deployed but had not issued any certificates. The company said it had no evidence that the weak keys had been recovered or exploited before disclosure.
These findings are important in distinguishing the seriousness of the cryptographic flaw from evidence of actual exploitation. Although the weakness created a potential security risk, the company has not reported confirmed malicious use of the affected keys.
Browser providers responded with measures to block the affected certificates and reduce the risk to users. Apple began blocking the affected intermediate certificates on October 19 and said its devices automatically receive the relevant protections. Mozilla blocked the affected certificates in Firefox and issued additional updates for users whose configurations might prevent them from receiving the protections. Google implemented blocking measures in Chrome and supported Android devices and announced the removal of the emSign ECC Root CA – G3 from the Chrome Root Store.
The removal of the root certificate could have wider implications than the revocation of the eight intermediate authorities alone. Some otherwise legitimate certificates that chain to the affected root may no longer be trusted by systems that remove it from their trust stores. Google said the Chrome Root Store change was expected to reach relevant devices on October 27, 2026. The precise impact depends on the browser, operating system, application and certificate chain involved.
eMudhra said its Indian digital-signature and eSign services, along with its enterprise applications, operate on separate infrastructure and were not affected. The company is arranging replacement certificates for affected customers at no cost and has offered certificates issued by Sectigo as an alternative. It also said its G1 RSA root certificates would continue to serve customers while the transition away from the global SSL/TLS business is completed.
For organisations using certificates associated with the affected hierarchy, the immediate priority is to identify potential dependencies, obtain replacement certificates where necessary and verify that websites and applications continue to function across browsers and devices. Administrators should also review systems that maintain independent certificate trust stores, as they may not receive the same protections automatically.
The incident raises broader questions about cryptographic implementation, operational oversight and the effectiveness of security audits. The failure to detect weak keys across two independent audit cycles highlights the importance of testing not only the intended cryptographic algorithms but also the procedures used to generate and manage their keys.
It also demonstrates how a technical error within a single certificate authority can trigger a coordinated response across the internet’s trust infrastructure, requiring action from browser providers, businesses and system administrators.
The eMudhra case underscores a fundamental principle of cybersecurity:trusted digital identities depend not only on strong cryptographic algorithms but also on correctly implemented key-generation procedures, rigorous testing and a coordinated response when vulnerabilities are discovered.
