Breach
eMudhra revokes eight more intermediate CAs after October key compromise
According to The Hacker News, eMudhra has revoked eight more intermediate certificate authorities that it had earlier said were unaffected by its October key compromise.
Written by a model from the sources below. Verify against them.
- Vendor
- eMudhra
- Status
- Confirmed
- Disclosed
- Data taken
- 195 records
Summary
The company says the flaw was a single line in an in-house Python script, and the newly revoked CAs had their keys compromised by that script even though their keys were not weakened.
What to do
Check whether your organization relies on certificates issued by eMudhra's intermediate CAs
Confirm the revocation status of any eMudhra-issued certificates you use
Replace certificates that chain to revoked eMudhra intermediate CAs
Watch eMudhra's advisories for further revocations
Watch eMudhra's advisories for the full investigation findings.
Timeline
- Made public by The Hacker News
- First seen by cve.now
- Confirmed by eMudhra
BleepingComputer: “In a new incident report published Tuesday, eMudhra said that both sets of certificates were affected by a custom Python script used to transfer private keys b…”
What was taken
195 records, perThe Hacker News
| Taken | Per the source |
|---|
Evidence 3
- PressThe Hacker News
“The in-house Python script behind eMudhra's October key compromise has now cost the company 8 more of its intermediate certificate authorities (CAs), even though it did not weaken their keys.”
- Social
- PressBleepingComputer
“Certificate authority eMudhra has revoked eight additional intermediate CA certificates after an investigation into its recent certificate security incident found improper handling of private keys during the certificate-generation process.”
+1 more: BleepingComputer on Bluesky
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about the eMudhra breach
Was eMudhra breached?
Yes. eMudhra says so: “In a new incident report published Tuesday, eMudhra said that both sets of certificates were affected by a custom Python script used to transfer private keys between hardware security modules (HSMs) in April 2025.” (BleepingComputer).
What data was exposed?
195 records.
What should eMudhra customers do?
Check whether your organization relies on certificates issued by eMudhra's intermediate CAs. Confirm the revocation status of any eMudhra-issued certificates you use. Replace certificates that chain to revoked eMudhra intermediate CAs. Watch eMudhra's advisories for further revocations. Watch eMudhra's advisories for the full investigation findings.