Export
The link always opens the latest version of this page.
Ask an AI about it
Open in ChatGPTA new chat that reads this entry from the site Open in ClaudeThe same, in ClaudeShare the link instead of a file, and they will always see the latest version.
Files are a snapshot of today. The live page has anything newer.
eMudhra certificate revocation incident
eMudhra is a certificate authority that experienced a key generation failure affecting its intermediate CA certificates.
On October 17, 2026, according to reporting, eMudhra discovered that eight intermediate TLS and code-signing CA certificates had been generated with cryptographically weak private keys 1. The root cause was identified as a scripting error in the hardware security module key generation process that produced private keys only one byte long instead of the required length 2.
The compromised intermediate certificates contained private keys with severely insufficient entropy. Reporting indicates the TLS certificates possessed 3–237 bits of entropy instead of the required 384 bits 3, while some keys were generated with fewer than 32 significant bits 4. One source reports that weak P-384 keys could be recovered with as few as 256 cryptographic tests 5.
eMudhra revoked the eight affected intermediate CA certificates 2. However, one intermediate CA remained in production, though reporting states no end-entity certificates had been issued from it 1. The incident potentially affected approximately 30,800 records 1.
The security implications were severe: recoverable CA private keys could enable attackers to issue fraudulent certificates appearing legitimate, allowing them to impersonate servers and intercept encrypted traffic. This posed particular risk to VPN users and non-browser TLS connections, especially in jurisdictions where governments conduct traffic interception 3.
The affected population included Web PKI users holding hundreds of millions of personal signing certificates and hundreds of web certificates 2, with one source identifying a single customer ecosystem in the United States as impacted 1.
The incident highlighted critical risks in certificate authority key generation infrastructure and the cascading security failures possible when HSM automation contains errors.
Facts 4
| Attribute | Value | Confidence | Sources | Cited |
|---|---|---|---|---|
| Date | 2026-10-17 | low | 1 | 1 |
| Victim | Web PKI users; hundreds of millions of personal signing certificates issued; hundreds of web certificates
also reported: Single customer ecosystem in the United States (low), VPN users and non-browser TLS connections, especially in countries with governments likely to intercept traffic (low)
|
low | 1 | 2 |
| Impact | private keys generated with fewer than 32 significant bits
also reported: Eight TLS certificates with private keys containing 3–237 bits of entropy instead of required 384 bits (low), Recoverable certificate-authority keys could be used to make fake certificates appear legitimate (low), Sixteen subordinate CA key pairs generated with truncated private keys; attackers could issue fraudulent certificates to impersonate servers and intercept traffic (low), Eight intermediate TLS and code-signing certificates discovered to use trivially weak private keys (low), Eight intermediate TLS CAs with weak cryptographic keys; one in production but no end-entity certificates issued (low), Eight intermediate CA certificates compromised; weak P-384 keys recoverable with 256 tests (low), Eight intermediate CA certificates revoked; private keys one byte long due to HSM key generation scripting error (low)
|
low | 1 | 4 |
| Records affected | 30800 | low | 1 | 1 |
Neighbourhood
Targets 1
Uses 1
Frequently mentioned together 14
Sources 10
- eMudhra Statement on Recent Certificate Security Incident · Lobsters
- podcast SANS Stormcast Wednesday, October 21st, 2026: eMudhra Intermediate CA Certificates Revoked; Critical PHP Security Release; Oracle CPU E-Business Suite SQLi (CVE-2026-101767); FortiSIEM gRPC RCE PoC · SANS ISC: Daily Podcast
- Compromised TLS Certificates · Schneier on Security
- Why not set MSB=1 for ECC Keys? · r/crypto
- Mozilla, Google, Apple block compromised eMudhra CA certificates · BleepingComputer
5 of 10 sources shown · Pro unlocks the full list