Eight Bits of Trust; eMudhra's CA keys cracked in milliseconds

The default trust settings on your non-browser applications and devices may be insecure for up to 17 months.

Security researcher Scott Helme discovered that eight of eMudhra's intermediate certificate authority (CA) private keys were compromised due to extreme weakness. Instead of being a robust 384-bit number, the keys were effectively single-byte values (e.g., 4, 56, 115). Helme was able to recover these keys in under a second from public certificates. This vulnerability affected six TLS issuing CAs and two code-signing CAs, all created in April 2025 and cross-signed by Sectigo. Major browsers like Chrome and Firefox acted quickly, blocking the affected intermediates and roots. However, the issue remains critical for many non-browser TLS clients, such as curl, Python, Node.js, and Java, as well as IoT devices, which often do not perform revocation or Certificate Transparency checks by default and may have un-updatable CA bundles.

The discovery reveals a critical flaw in the fundamental security model of certificate authorities, where weak private key generation can render vast swathes of the internet infrastructure vulnerable. While major browsers have mitigated the risk by blocking the compromised eMudhra keys, the majority of other TLS clients and embedded systems remain at risk because they do not perform necessary security checks like Certificate Transparency or revocation. This incident highlights the significant challenges in securing the broader software ecosystem beyond web browsers. The long lifespan and lack of update mechanisms for many IoT devices, alongside the default configurations of common command-line tools and programming language libraries, mean that a significant attack surface remains exposed, potentially for years to come.

The compromise underscores the ongoing tension between ease of use and robust security in digital trust systems. The fact that simple, single-byte keys were generated and used for critical CA functions points to potential systemic oversights in eMudhra's key management processes. Furthermore, the broad impact on non-browser clients reveals a widespread dependency on CA bundles that are not regularly updated or verified for revocation status, leaving many systems susceptible to forged certificates without user intervention.