eMudhra Revokes 16 Intermediate CAs and Quits Public TLS After a Botched HSM Migration Left Eight CA Private Keys Below 256 — One Was Literally the Number 4

High · 2026-11-15 · By H.A

eMudhra Revokes 16 Intermediate CAs and Quits Public TLS After a Botched HSM Migration Left Eight CA Private Keys Below 256 — One Was Literally the Number 4

A buggy key-migration script shrank eight ECDSA intermediate keys to a single byte, forcing browser distrust, 16 revocations and a G1 issuance stop on 16 November, though eMudhra reports no evidence of misuse.

Overview

Indian certificate authority eMudhra has now revoked 16 intermediate CA certificates and will leave the publicly trusted TLS certificate business. The trigger was the discovery that eight of its ECDSA P-384 intermediate private keys were tiny integers below 256. That made them recoverable by trying just 256 values. One of them, belonging to the "EM OV TLS CA - G3C" intermediate, was the number 4.

Anyone who recovered these keys could have issued TLS certificates for any website, or code-signing certificates, that browsers and operating systems would trust. eMudhra says most of the affected intermediates were never used in production, and it has found no evidence the keys were abused. But the weak keys existed from April 2025 until October 2026, so the window for silent misuse was long.

The Vulnerability

In April 2025, hardware delays forced eMudhra to move CA private keys between hardware security modules (HSMs) from different vendors. It used a custom Python script during the key ceremony. eMudhra's investigation found the script had two problems:

eMudhra never checked the strength of the generated keys, or that the keys used to create certificate signing requests matched the ones created in the HSM. There was an early warning: in mid-2025, certificate revocation lists for some intermediates were signed with keys that did not match the CA certificates. eMudhra fixed that symptom without finding the cause.

Affected ECDSA intermediates, revoked for CA compromise: EM DV TLS CA - G3B and G3C, EM EV TLS CA - G3B and G3C, EM OV TLS CA - G3B and G3C, and the code-signing EM OV CS CA - G3B and G3C. Sectigo also revoked its cross-signatures for the same CAs.

Timeline

All times are Mauritius time (UTC+4), with UTC in brackets.

Tradecraft

This is not an attack campaign. It is a trust-infrastructure failure that an attacker could have exploited quietly. Abuse would have looked like this:

Detection

# Show the issuer chain presented by a server
openssl s_client -connect example.com:443 -servername example.com -showcerts </dev/null 2>/dev/null | grep -E "s:|i:"
# Check a local certificate file
openssl x509 -in cert.pem -noout -issuer -subject -dates
# Windows: look for emSign/eMudhra certificates in the machine stores
Get-ChildItem Cert:\LocalMachine -Recurse | Where-Object { $_.Issuer -match "emSign|eMudhra|EM (DV|OV|EV)" } | Select Subject, Issuer, NotAfter, Thumbprint

Recommended Actions

Analyst Assessment

There is no evidence of exploitation. But a publicly trusted CA key equal to 4 is one of the most serious trust failures in years. The browser root programmes responded within hours of the report, which limited exposure. The eighteen months the weak keys existed beforehand is the uncomfortable part.

eMudhra's exit from public TLS is the likely outcome, and root-store operators will probably tighten requirements on key-ceremony verification. For most organisations the practical risk is now operational: migrating certificates and re-signing code before the 16 November and later deadlines catch them out.

REEF SENTINEL