Incident · critical · CVSS 9.3
eMudhra intermediate CA key compromise leads to revoked certificates and pip certifi bundle issue
Tier B · Patch this week – Put it in the sprint
Who’s exposed: Systems trusting certificates issued by eMudhra intermediate CAs
Tier B because: Full takeover OR secrets exposed OR supply chain
Reach
Attack
Damage
Fix
Remote, no login · Full takeover · Secrets exposed · No fix yet
What to do
- Check whether any certificates you rely on chain to the revoked eMudhra intermediate CAs and replace them.
The Brief
- eMudhra has revoked 8 more intermediate CA certificates after its investigation found improper private key handling during certificate generation.
- The company says an in-house Python script caused the October key compromise, and the 8 newly revoked CAs were previously declared unaffected even though their keys were not weakened.
- eMudhra's official incident report was posted on Bugzilla, and a Czech developer has published reworked certificates to block smart TV ads.
Why it matters
Developers and systems that trust certificates chaining to eMudhra's intermediate CAs may find those certificates revoked or unsafe, which can break TLS or signing workflows.
The checklist behind the tier
Checklist · 5 of 10 yes
| Yes | Hits tech teams | Judgment: certificate authorities issue certificates that developers and IT teams rely on for signing and TLS. |
| No | Core infrastructure | Judgment: a regional CA like eMudhra is not software nearly every team runs. |
| No | Popular tool | Judgment: eMudhra is a niche CA, not a widely used framework, tool or platform. |
| No | Exploited in the wild | Sources describe key mishandling and revocations; none report observed attacks using the flaw. |
| No | Public exploit | Sources describe an internal script bug and an incident report; no public exploit or PoC is mentioned. |
| Yes | Remote, no login | CVSSCVE-2026-133949: CVSS 9.3 – network, no privileges, no user interaction |
| Yes | Full takeover | CVSSCVE-2026-133949: CVSS rates confidentiality and integrity impact high |
| Yes | Secrets exposed | The Register: eMudhra's private key exposure; Hacker News: intermediate CA private key compromise. |
| No | Supply chain | Sources report weak certificates from a buggy script, not malicious code shipped through a trusted channel. |
| Yes | No fix yet | The Register calls eMudhra a former CA; it revoked 8 more CAs, with no fixed version reported. |
The official record
From CVE.org, CISA’s Known Exploited Vulnerabilities catalog, FIRST EPSS and the GitHub Advisory Database. Where these answer a checklist fact, they win over the reporting.
CVE-2026-133949 ↗CVSS 9.3 critical AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
pip bundles compromised eMudhra certificates via certifi
- Exploited
- Not in CISA’s exploited catalog
- EPSS
- <1% chance of exploitation in the next 30 days · higher than 46% of all CVEs
- Weakness
- CWE-295
Timeline
Full coverage · 8 sources
- 20h ago ↗
Open Source Security
[oss-security][CVE-2026-133949] pip bundles compromised eMudhra certificates via certifi - 9d ago ↗
www.theregister.com - Articles
Software Samaritan revamps borked Indian certs to block smart TV ads - 9d ago ↗
www.theregister.com - Articles
Disgraced former CA eMudhra blames buggy script for hopelessly weak certificates - 10d ago ↗
BleepingComputer
eMudhra revokes 8 more CA certificates after private key mishap - 10d ago ↗
top scoring links : programming
eMudhra's official incident report on how they ended up with private key 4 - 10d ago ↗
- 16d ago ↗
Python Software Foundation News
How the Python ecosystem responded to the eMudhra intermediate compromise - 17d ago ↗
foojay.io - Friends Of OpenJDK
Java Patching at Incident Speed: Lessons from the eMudhra CA Compromise
First seen · 8 sources · Full story page · How tiers are decided