eMudhra Key Collapse Exposes Systemic Trust Gaps

A critical failure in the trust architecture of eMudhra has left a 17-month window of vulnerability open for digital transactions and software updates, as first reported by security researcher Scott Helme. Helme found that eight of eMudhra's intermediate certificate authority (CA) private keys were created as inherently weak single-byte keys, allowing them to be cracked in milliseconds using commodity hardware.

According to Helme, while P-384 private keys should be random 384-bit numbers, eMudhra's keys consisted of 47 bytes of zeros followed by a single byte. This reduced the security model from trillions of possibilities to a maximum of 255 steps. The compromised keys include two code-signing CAs and six TLS issuing CAs (DV, OV, and EV) created in April 2025, all of which were cross-signed by Sectigo's AAA Certificate Services root in May 2025.

While major browser vendors responded quickly, the systemic risk remains. Reporting from Helme notes that on October 17, a researcher alerted Apple, Google, Microsoft, Mozilla, and eMudhra. Chrome and Mozilla subsequently blocked the intermediates via CRLSet and OneCRL, and Mozilla later removed the eMudhra root.

However, the vulnerability extends beyond browsers. Helme warns that most non-browser TLS clients—including Python, Java, Node, Go, and git—typically trust CA bundles on disk without checking revocation or Certificate Transparency (CT) by default. This exposes critical infrastructure, such as CI/CD pipelines and IoT firmware updaters, to potential attacks where forged certificates could allow the execution of malicious code as root.