A private key is supposed to be an astronomically large, unguessable number. One of the eight that eMudhra Limited generated for its certificate authorities in April 2025 was the number 4. That single fact, disclosed to browser makers on 17 October 2026, has led to the revocation of eight certificate authorities, emergency blocking action by every major browser, and now a set of formal representations seeking an incident report, an independent audit and regulatory scrutiny from eMudhra, CERT-In and the Ministry of Electronics and Information Technology.
A trust system undone by weak arithmetic
Certificate authorities exist to vouch for identity online. When a browser confirms that a connection to a bank or government portal is secure, it is relying on a signature made with that authority's private key, a number that is supposed to be so large and so randomly chosen that no one could ever reproduce it. eMudhra, a Bengaluru-based company licensed by India's Controller of Certifying Authorities and also trusted internationally through its emSign roots, generated eight such keys at a single ceremony in April 2025. According to eMudhra's own account, a flaw in the ceremony script produced a second, weak set of keys on the hardware security module, and because the labelling was similar, those weak keys were used instead of the intended ones. The result was keys that were, in practical terms, public from the moment the certificates were issued. A researcher recovered all eight in under a second simply by trying small numbers in sequence.
A fast response from browsers, a slower one from everyone else
Google, Mozilla, Apple and Microsoft moved within three days of the disclosure, blocking the affected certificate authorities in their respective browsers, and eMudhra revoked all eight intermediates on 18 October. That speed reflects safeguards built into modern browsers: they receive revocation information automatically and require website certificates to appear in public Certificate Transparency logs before trusting them. Those logs show no evidence that any certificate was ever issued using the compromised keys, which is some reassurance. But the same protections do not exist uniformly across the wider software ecosystem. Many applications, embedded systems and older platforms do not check revocation status at all, and they will continue trusting these certificate authorities until they are separately patched or updated, a process that could take considerably longer than the three days it took browsers to act.
Warning signs that went unheeded
What makes the episode more troubling than a single engineering mistake is the evidence that eMudhra had reason to suspect a problem well before the public disclosure. In May 2025, shortly after the flawed ceremony, the company issued revocation lists for the same six website-facing intermediates that carried invalid signatures. Rather than treating that as a signal that the wrong keys were in use, eMudhra has acknowledged that the lists were "resigned with flawed keys" to make the error disappear from view. A properly audited key ceremony, of the kind eMudhra itself commissioned for its root certificate authorities in February 2024, with an independent observer present and the generation script reviewed line by line, would likely have caught a key as small as the number 4 before it was ever embedded in a certificate. No equivalent independent scrutiny appears to have accompanied the April 2025 ceremony.
Why this matters beyond one company
eMudhra says its Indian digital signature and eSign operations, which rely on a separate licensing regime under the Information Technology Act, are unaffected, and that none of the compromised keys were ever used to sign a certificate. Those claims may well hold up. But the incident exposes a structural weakness in how trust is distributed across the internet: a single certificate authority's internal process failure can cascade into a global security event within hours, while the authority responsible faces scrutiny that is largely voluntary and technical, conducted on a public bug tracker rather than through a formal regulatory channel. CERT-In issued an advisory on 21 October, but no statement has yet come from the Controller of Certifying Authorities, the body actually responsible for licensing eMudhra to operate in India. That gap, between a company's own account of events and independent verification by the regulator meant to oversee it, is precisely what the representations sent on 21 October are intended to close.