Indian certificate authority eMudhra disclosed a critical security flaw that left eight of its intermediate certificates vulnerable to immediate key recovery. The weakness stems from private keys that were far smaller than industry standards, enabling an attacker to guess each key in under a second and potentially forge HTTPS certificates for any domain.
Discovery and public disclosure
The vulnerability was uncovered on October 17 by a security researcher known only as Wayne, who was conducting routine checks against the Common CA Database (CCADB). To demonstrate the severity of the issue, Wayne signed the phrase “We have a problem here – Wayne” with each compromised key and forwarded the findings to major platform owners, including Apple, Google, Microsoft, Mozilla, and eMudhra itself.
Mozilla’s security lead Dennis Jackson made the incident public on October 20 via the organization’s dev‑security‑policy forum. Jackson warned that the compromised keys could allow malicious actors to issue fraudulent HTTPS certificates for sites they do not control, as the intermediates chain to root certificates trusted by the four major browser vendors.
Technical details of the key weakness
According to Mozilla’s incident report, the eight affected intermediate certificates were part of a batch of 24 generated on April 30, 2025. Six of the intermediates were intended for TLS website certificates and two for code‑signing. All eight were cross‑signed by the global CA Sectigo in May 2025.
Standard practice requires a private key to be a random number exceeding 100 decimal digits, providing sufficient entropy to resist brute‑force attacks. In eMudhra’s case, each key was less than 256 in value. This means an attacker needs to test at most 256 possible numbers to recover the key—a task that can be completed in a fraction of a second on ordinary hardware.
Security researcher Scott Helme confirmed the ease of recovery. He posted the exact values he uncovered, noting that one key was literally the number “4”, another “56”, and a third “115”. Helme emphasized that, unlike typical key compromises that involve theft, these keys were effectively public from the moment the certificates were issued.
Browser response and revocation timeline
Following the disclosure, major browsers acted swiftly. Chrome and Firefox blocked the eight intermediates on the day of the report. Apple removed trust on October 19, and Microsoft followed on October 20. eMudhra revoked the certificates on October 18, a day after the initial finding.
Despite the rapid browser response, Jackson cautioned that the incident’s impact could be severe for devices and applications lacking reliable revocation mechanisms. He highlighted the risk that such systems might continue to trust the compromised certificates, leaving user traffic exposed to interception or modification.
After multiple independent recoveries of the keys, Mozilla removed trust in the eMudhra root certificate that signed the intermediates. Google announced a similar move for Chrome and indicated a “thorough evaluation” of any remaining eMudhra CA certificates. eMudhra has ceased issuing new certificates from the affected root and estimates that roughly 30,000 customer certificates will need to be replaced.
Root cause and remediation efforts
eMudhra traced the flaw to a faulty script used during the April 2025 key‑generation ceremony. The script inadvertently produced a second set of weak keys whose labels resembled those of the correctly generated keys. Staff, unaware of the duplication, selected the weak keys when preparing the certificates for issuance.
The company asserted that only one of the eight intermediates ever entered production and that none were used to issue certificates to external customers. Nevertheless, eMudhra admitted to human errors at several stages of the process and pledged to audit every key ceremony it has performed to date.
It remains unknown whether any party exploited the weak keys during the 17 months between their creation and public reporting. Security experts warn that applications, servers, or embedded devices that do not receive timely revocation updates could still trust the compromised certificates, potentially exposing sensitive data.
Industry reaction and recommendations
Cloudflare described the incident as “a serious security incident with implications across the Internet.” The company noted that the weak keys allowed attackers to forge certificates for any domain, enabling man‑in‑the‑middle attacks against traffic routed through Cloudflare’s network.
Helme recommended that administrators update the certificate trust stores used by their systems and urged users to ensure their browsers and operating systems are current. Mozilla’s disclosure page also advises users to apply the latest updates to mitigate any lingering risk.
The eMudhra episode underscores the importance of rigorous key‑generation procedures and robust verification steps in public‑key infrastructure. As digital certificates continue to underpin secure web communication, even a single misconfiguration can ripple across the global internet ecosystem, affecting browsers, cloud providers, and end‑users alike.
Be First to Comment