TBNSecurity
Compromised TLS Certificates
Publication: Schneier on Security
Author: Bruce Schneier
Source published: 23/10/2026, 11:04:22 UTC
Briefing created: 23/10/2026, 11:17:48 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 23/10/2026, 11:15:24 UTC.
Briefings
An investigation reveals eight TLS certificates issued by eMudhra Limited, India, containing private keys with only 3 to 8 bits of entropy, far below the 384-bit standard. This severe cryptographic weakness, likely caused by a misconfigured key generation interface, exposes the entire certificate regime to immediate threats for VPN users in countries with hostile governments. While eMudhra representatives were unavailable, the incident highlights systemic failures in certificate issuance and the need for enhanced transparency monitoring.
Key points
- Eight TLS certificates issued by eMudhra Limited contain private keys with only 3 to 8 bits of entropy, drastically below the required 384-bit standard.
- The compromised keys likely resulted from a misconfigured key generation interface, potentially allowing example code to leak into production environments.
Context
This incident represents the latest failure in the TLS certificate regime, exposing a fatal flaw where certificates are as strong as their weakest link. The specific weakness stems from eMudhra's compromised keys, which are now a critical vulnerability for any active adversary-in-the-middle attack targeting VPN users in countries with malicious governments.
Limitations
Evidence is limited to the eight compromised certificates and expert analysis from Valdorda and Ben Cartwright-Cox. The exact root cause remains uncertain, with speculation ranging from a misconfigured 'size' parameter to accidental code leakage. eMudhra representatives were unavailable, and the full scope of other affected cases is unknown.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 23/10/2026, 11:17:48 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeicfqagssneb6kb3qso6e2itdybsrsurowwlgy5kgcp33omhtjcjsu