"Each of the eight eMudhra keys was a whole number below 256, with one simply logged as the number 4."
How the weakness made private keys trivial to reconstruct
Security researchers notified major browser vendors last week after finding that eight intermediate certificates issued by Indian certificate authority eMudhra were generated with so little randomness that their private keys could be computed from the public certificates in seconds. The normally enormous private numbers for this form of cryptography — roughly 77 or 78 digits long — were instead tiny integers. Researcher Scott Helme recovered all eight on his laptop in less than a second, and he said an AI agent later repeated the reconstruction from a single prompt.
eMudhra attributed the flaw to an error during a key generation ceremony held in April 2025. According to the company, the mistake produced a second, weak set of keys that was published to browser trust lists instead of the intended set. Because a certificate publicly displays the key it was built from, anyone could test the small set of possible values in seconds and use the resulting keys to forge certificates and impersonate sites.
Browser and platform responses
The discovery triggered rapid action from platform and browser vendors. Chrome and Firefox blocked the certificates within hours of the report; Apple blocked them on Monday and Microsoft followed on Tuesday. Mozilla removed eMudhra’s root certificate from its trusted list. Google said it will remove that root from Chrome in an update expected next week while it reviews eMudhra’s remaining root certificate.
Language runtimes and operating-system distribution channels also moved: Go, Node.js, Python’s certifi bundle and several Linux distributions shipped updates to reflect the trust changes. The company said none of the eight intermediates had issued end-entity certificates, and whether anyone used the weak keys is not known.
Your scanner finds 4,000 vulns. Which 12 matter?
Nubivance is a Rapid7 Registered Partner delivering vulnerability management as a service - scanning, risk-based prioritization, and remediation follow-through across IT and OT.
Fix the backlogeMudhra's board shutters the SSL/TLS unit
Days after the flaw became public and browsers blocked the certificates, eMudhra announced it will stop issuing SSL/TLS certificates. The company said its board concluded, "after detailed deliberations," that leaving the business was the right decision for eMudhra and its shareholders.
Company Chairman V. Srinivasan cited several reasons: rising costs from data sovereignty and compliance requirements, competition from large providers that issue certificates free of charge, and social media amplification that brought scrutiny "out of proportion" to the unit’s place in the company. eMudhra framed the decision in corporate terms: "For many certifying authorities, SSL/TLS is the whole business," the company said. "For eMudhra it is one part of a much broader digital solutions portfolio."
The company also said its infrastructure had not been compromised, that no data was breached, and reiterated that none of the eight intermediates had issued end-entity certificates. Indian authorities launched an investigation, and CERT‑In reported it had not seen malicious use of the keys as of Wednesday. Still, eMudhra acknowledged reputational risks it cannot quantify, and shares of the company fell 40% in the two days after the vulnerability was disclosed.
How technologists, policymakers, and enterprises should be thinking
- Technologists and security teams: Expect continued churn in trust stores and runtime updates. The immediate operational task is applying the updates already issued by browsers, language runtimes and Linux distributions, and auditing certificate inventories for any dependencies on eMudhra intermediates.
- Policymakers and regulators: CERT‑In’s involvement and eMudhra’s reference to data sovereignty and compliance costs highlight regulatory and governance dimensions that contributed to the company’s strategic calculation. Regulators will likely monitor the investigation and the broader implications of critical-ceremony failures.
- Affected enterprises and procurement leaders: eMudhra says its other businesses — digital signature and enterprise security services — continue to operate normally, and the company asserts the impacted intermediates did not sign end-entity certificates. Still, organizations that relied on eMudhra for TLS or certificate supply should complete inventories and confirm their trust chains are no longer linked to the removed intermediates or root.
Investigations, removals, and the unanswered question of use
Browsers and platforms have acted decisively to remove trust and push out updates; eMudhra has exited the market segment; and Indian authorities are investigating. Yet core factual gaps remain in the public record: whether the weak keys were ever used to issue forged certificates, who — if anyone — might have exploited them, and what specific procedural failures at the April 2025 ceremony allowed a second, weak key set to be published.
The immediate technical risk has been reduced by the removals and updates, but the episode underscores how a single procedural error in key generation can produce disproportionate operational and financial consequences — up to a 40% share-price drop over two days and the company’s retreat from a line of business. With Google planning a further removal in Chrome and Mozilla having already axed the root, the coming week will show whether further trust changes or regulatory findings alter the picture.
