EIGHT TLS intermediate certificates belonging to India-based CA eMudhra Limited have been found with dangerously weak private keys that could allow an attacker to mint trusted credentials for any site. By late morning on 20 October 2026, browser makers and several major apps and programming languages had blocked all eight intermediates.
There were no reported uses in certificate transparency logs so far, but the flaw risks are broad, as updating all affected systems across Linux distributions, embedded devices and IoT could be extremely time‑consuming.
The exposed private keys were extraordinary in their weakness. Normal private keys on a NIST P-384 elliptic curve would have around 384 bits of entropy, but the compromised keys ranged from 4 to 237 bits, with actual sizes 4, 56, 66, 115, 155, 156, 230 and 237. Analysts warned that remediation will be a prolonged “cleanup job” affecting VPNs and many non-browser TLS implementations, including forgotten Linux hosts and containers where root certificates are baked in.
Edge reportedly remained connected to about a dozen vulnerable hosts at the time, while Signal, WhatsApp and WireGuard were not affected because they do not rely on TLS for confidentiality. The incident highlights the TLS system’s fragility when a single CA’s keys are defective, and while transparency logs help detect misissuances, prevention depends on widespread, coordinated patching and re‑issuance efforts that are only just beginning.