Story
Oct 23, 2026
eMudhra’s Tiny Keys Triggered a Fast Browser Fix—and a Much Slower Internet Cleanup
Eight catastrophically weak eMudhra TLS keys set off an emergency response, with browsers blocking them quickly. But the certificate authority’s retreat from TLS does little to solve the longer repair job across outdated systems and embedded devices.
The alarm sounded after researchers found eight eMudhra intermediate TLS certificates whose private keys were so weak that anyone could derive them and issue browser-trusted certificates for virtually any website or mail server. Instead of the enormous randomness expected of P-384 cryptography, the exposed keys ranged from just 3 to 8 bits—values including 4, 56 and 237.1
By Tuesday, browser makers and some major applications and programming languages had blocked all eight certificates. There was no reported evidence in certificate-transparency logs that the keys had been abused. But the rapid browser response only contained the most visible part of the problem: Linux distributions, IoT gear, containers and neglected machines can carry their own outdated trust stores.1
Cryptography engineer Filippo Valsorda warned that the repair effort could be worse than Heartbleed, citing the sprawling mix of devices and administrators involved. “Every time you need a lot of different people in different contexts to do something, it will take a long time,” he said.1 The threat is especially acute where attackers can position themselves between users and services, such as hostile local networks or state-backed interception efforts.
Two days after the discovery, eMudhra offered its explanation. It said an April 30, 2025 key-generation ceremony produced proper keys, but an approved wrap/unwrap test created a second, weak set; similar labels then led staff to use those keys for certificate requests and cross-signing. The company acknowledged “human errors in multiple steps” and said it would reverify every key ceremony.2
On Thursday, eMudhra said it would withdraw from global SSL/TLS, arguing that rising compliance costs, free certificates and a business contributing only 1% of revenue made the operation untenable. It also said social-media scrutiny had become disproportionate to TLS’s role in its business.2 Yet its exit does not revoke trust from systems that cannot be promptly updated—leaving the internet’s weakest, oldest corners to catch up.