Summary
- Eight eMudhra intermediate certificate private keys were so weak they could be reconstructed in under a second; one key had a value of just 4.
- Major browsers — Chrome, Firefox, Apple, and Microsoft — blocked the certificates within days of disclosure; Mozilla removed eMudhra’s root certificate from its trusted list.
- eMudhra says none of the eight affected intermediates issued end-entity certificates and no data was breached, though whether the keys were misused externally remains unknown.
- The flaw was attributed to an error during a key generation ceremony in April 2025 that produced a second, unintended weak key set published to browser trust lists.
- eMudhra’s board has resolved to exit the SSL/TLS certificate business entirely; the company’s shares fell 40% in the two days following disclosure.
What happened
Indian certificate authority eMudhra has announced it will cease issuing SSL/TLS certificates following a disclosure that eight of its intermediate certificate private keys were trivially recoverable. Security researcher Scott Helme reconstructed all eight keys on a personal laptop in less than a second. He subsequently demonstrated that an AI agent could repeat the task from a single prompt.
The nature of the flaw
The vulnerability was fundamental. A standard private key for this class of cryptography is a number roughly 77 to 78 digits long — computationally impossible to guess by brute force. Each of the eight affected eMudhra keys was a whole number below 256. One was simply the number 4. Because a certificate publicly discloses the mathematical parameters it was built from, any attacker could test every possible value in seconds and recover the corresponding private key. Such a key could be used to forge certificates and impersonate arbitrary websites.
Origin of the error
eMudhra attributed the flaw to a key generation ceremony conducted in April 2025. The company says the process produced a second, unintended set of weak keys, and it was this set — rather than the intended strong keys — that was submitted to and accepted by browser trust lists. The company stated that its infrastructure was not compromised and that no data was breached. It also said none of the eight affected intermediate certificates had been used to issue end-entity certificates. Whether the exposed keys were exploited by any third party before disclosure is not known.
Browser and ecosystem response
The ecosystem response was swift. Chrome and Firefox blocked the certificates within hours of the initial report. Apple followed on Monday and Microsoft on Tuesday. Mozilla went further, removing eMudhra’s root certificate from its trusted list entirely. Google has announced it will remove that root from Chrome in an upcoming update while it reviews the company’s one remaining root certificate. Beyond browsers, Go, Node.js, Python’s certifi bundle, and several Linux distributions also shipped remediation updates. India’s computer emergency response team, CERT-In, said as of Wednesday it had not observed any malicious use of the keys.
The business outcome
eMudhra’s board concluded that exiting the certificate business was the appropriate course of action for the company and its shareholders. Company Chairman V. Srinivasan cited rising compliance and data sovereignty costs, along with competitive pressure from providers offering certificates at no charge. He also noted that social media coverage of the incident had drawn scrutiny he considered disproportionate to the division’s contribution to the overall business. The company pointed out that SSL/TLS certificate issuance represented one component of a broader digital solutions portfolio — distinct from its digital signature and enterprise security services, which it says continue to operate normally. The company acknowledged reputational risks it cannot currently quantify. Shares fell 40% across the two trading days following the disclosure.
Why it matters
This incident is a case study in how a single procedural failure at a point of trust — a certificate key generation ceremony — can cascade into a business-ending event. For CISOs, the immediate operational question is whether any eMudhra-issued certificates remain in your environment or supply chain; the revocation and root removal actions taken across major browsers and runtimes may cause unexpected trust failures for internal or partner systems that have not yet updated their trust stores. More broadly, this episode is a reminder that certificate authority trustworthiness is binary in practice: once a root is removed from a browser trust list, the commercial and reputational damage is severe and largely irreversible. Organisations should review their certificate inventory management processes and confirm that CA selection criteria explicitly account for a CA’s key generation hygiene and audit transparency — not just price or convenience.
What to do now
- Audit your certificate inventory for any eMudhra-issued SSL/TLS certificates and replace them with certificates from a currently trusted CA.
- Verify that browsers, operating systems, runtimes (Go, Node.js, Python certifi), and Linux distributions in your environment have received the trust store updates that block the affected eMudhra certificates.
- Monitor for unexpected TLS errors in internal systems or partner integrations that may rely on trust stores not yet updated.
- Review your CA selection and procurement criteria to confirm that key generation ceremony practices and third-party audit reports are evaluated, not only cost.
- Check CERT-In advisories and your own logs for any indicators of certificate misuse during the window between April 2025 and the date of disclosure.
