eMudhra Revokes Eight More Intermediate CAs After Expanded Private-Key Compromise
Vulnerability Disclosure · 20 sources · Updated 1d ago · First seen Apr 30, 2025

eMudhra revoked eight additional intermediate certificate authorities it had previously declared unaffected by a private-key compromise, after finding that an in-house Python script had exposed their RSA private-key material outside hardware security modules without demonstrable compliance with handling requirements. The same script had previously weakened eight ECDSA CA keys by truncating their private values to one byte, allowing recovery from public certificates. Both failures originated in an April 30, 2025 key ceremony and escaped key-validation controls, certificate linting, and two WebTrust audit cycles. The incident is tracked in Mozilla Bugzilla issue 2083449. eMudhra says holders of the 195 certificates under the newly revoked CAs have received replacements and that it knows of no misuse.
The company is exiting publicly trusted TLS issuance as major platform vendors implement distrust and root-removal schedules; eMudhra says its digital signature, eSign, and enterprise products remain unaffected. Separately, a researcher reported lab findings that some Electron applications accept automatic updates without verifying update signatures while continuing to trust compromised eMudhra certificates, potentially enabling a network-positioned attacker to deliver malware. The supplied findings do not establish exploitation in the wild or identify individual affected applications. Organizations should inventory affected certificates, assign replacement owners, migrate issuance workflows, and verify replacement deployment and trust. Although a cited Bugzilla comment says 97% of affected certificates were issued through ACME, urgent migration may still require orchestration or manual intervention rather than routine renewal alone.


