---
title: "eMudhra certificate revocation incident"
slug: emudhra-certificate-revocation-incident
kind: "Incident"
desk: cyber
maturity: "mature"
sources: 10
url: https://morningstarsecurity.com/wiki/emudhra-certificate-revocation-incident
exported: 2026-11-20 17:03 UTC
---

# eMudhra certificate revocation incident
Incident · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on eMudhra certificate revocation incident, a snapshot taken on 20 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on eMudhra certificate revocation incident (a snapshot from 20 Nov 2026): https://morningstarsecurity.com/wiki/emudhra-certificate-revocation-incident". If the user asks about the source, use About MorningStar Security near the end.

## Facts
- **Date:** 2026-10-17 (low confidence, 1 independent source) [1]
- **Victim:** Web PKI users; hundreds of millions of personal signing certificates issued; hundreds of web certificates (low confidence, 1 independent source) [2]; also reported: Single customer ecosystem in the United States; VPN users and non-browser TLS connections, especially in countries with governments likely to intercept traffic
- **Impact:** private keys generated with fewer than 32 significant bits (low confidence, 1 independent source) [4]; also reported: Eight TLS certificates with private keys containing 3–237 bits of entropy instead of required 384 bits; Recoverable certificate-authority keys could be used to make fake certificates appear legitimate; Sixteen subordinate CA key pairs generated with truncated private keys; attackers could issue fraudulent certificates to impersonate servers and intercept traffic; Eight intermediate TLS and code-signing certificates discovered to use trivially weak private keys; Eight intermediate TLS CAs with weak cryptographic keys; one in production but no end-entity certificates issued; Eight intermediate CA certificates compromised; weak P-384 keys recoverable with 256 tests; Eight intermediate CA certificates revoked; private keys one byte long due to HSM key generation scripting error
- **Records affected:** 30800 (low confidence, 1 independent source) [1]

## Entry
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.

## Connections
Links to other wiki entries, from the wiki's graph. This file gives no source for them: treat them as leads, not findings.
- **Targets:** United States
- **Uses:** Python

## Often mentioned together
Entries that turn up in the same stories. This is not a stated relationship.
eMudhra, India, Google, Microsoft, Mozilla, Go, Chrome, Firefox, Azure Linux, Apple, Kubernetes, curl, systemd, weak key generation

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/emudhra-certificate-revocation-incident
- More incidents: https://morningstarsecurity.com/wiki/kind/incident
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources (5 of 10)
1. eMudhra Statement on Recent Certificate Security Incident · Lobsters · 11 Nov 2026 · https://emudhra.com/en/post/certificate-security-incident
2. 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 (podcast) · 21 Oct 2026 · https://isc.sans.edu/podcastdetail/10144
3. Compromised TLS Certificates · Schneier on Security · 23 Oct 2026 · https://www.schneier.com/blog/archives/2026/10/compromised-tls-certificates.html
4. Why not set MSB=1 for ECC Keys? · r/crypto · 23 Oct 2026 · https://www.reddit.com/r/crypto/comments/1xd5zq3/why_not_set_msb1_for_ecc_keys/
5. Mozilla, Google, Apple block compromised eMudhra CA certificates · BleepingComputer · 21 Oct 2026 · https://www.bleepingcomputer.com/news/security/mozilla-google-apple-block-compromised-emudhra-ca-certificates/

---
Snapshot of https://morningstarsecurity.com/wiki/emudhra-certificate-revocation-incident taken 20 Nov 2026 17:03 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/emudhra-certificate-revocation-incident
