Skip to main content
Mallory
← Back to News
identity-authentication-vulnerabilityinformation-technology-sector-threatleaked-secret-api-keybreach-disclosure-notification

eMudhra Revokes Eight More Intermediate CAs After Expanded Private-Key Compromise

Vulnerability Disclosure · 20 sources · Updated 1d ago · First seen Apr 30, 2025

eMudhra Revokes Eight More Intermediate CAs After Expanded Private-Key Compromise

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.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

18 events · Apr 30, 2025 – Nov 10, 2026
  1. Reported Nov 12, 20265d ago

    Developer uses compromised eMudhra key to replace Samsung smart TV ads

    Daniel Vrátil demonstrated HTTPS interception on his 2022 Samsung television, which still trusted compromised eMudhra CAs, by forging certificates for Samsung advertising domains and redirecting traffic to replace advertisements with family photos and discard tracking requests. He published the project on GitHub, demonstrating practical interception risks for devices retaining the compromised trust.

    Software Samaritan revamps borked Indian certs to block smart TV ads
  2. Reported Nov 12, 20266d ago

    eMudhra commissions independent KPMG audit after CA key-handling failures

    eMudhra commissioned KPMG to conduct an independent audit intended to identify improvements to its certificate-management and key-generation procedures. Findings were expected by December 4, 2026; the reference does not specify when the audit was commissioned.

    eMudhra отповика уште 8 CA-сертификати по пропуст при ракувањето со приватните клучеви | MKD-CIRT | Национален центар за одговор на компјутерски инциденти
  3. Reported Nov 11, 20266d ago

    Researcher discovers weak eMudhra keys and alerts browser root programs

    On October 17, researcher Wayne reportedly demonstrated possession of the eight weak private keys by signing messages and sent the evidence to Mozilla, Chrome, Apple, and Microsoft root-program teams. Mozilla independently reconstructed the keys within hours, confirming their trivial recoverability.

    eMudhra Revokes 8 More Certificate Authorities Following Major SSL Private Key Security Failure
  4. Reported Nov 11, 20266d ago

    Apple updates block compromised CAs in bundled command-line tools

    Apple said macOS 27.2.1, 26.7.3, and 15.8.3 prevent bundled tools such as curl and git from accepting the compromised TLS CA certificates. The updates also remove five roots, including emSign Root CA - G1, from /etc/ssl/cert.pem.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  5. Reported Nov 11, 20266d ago

    The Hacker News recovers all eight weak ECDSA private keys

    The Hacker News recovered all eight weakened ECDSA private keys from their public certificates. Their private values ranged from 4 to 237, demonstrating the impact of the script's one-byte truncation.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  6. Reported Nov 11, 20266d ago

    eMudhra reports replacement of certificates under the revoked RSA CAs

    eMudhra said all holders of the 195 listed certificates under the newly revoked RSA CAs had received replacements. The company reported no known misuse of the affected keys.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  7. Reported Nov 11, 20266d ago

    eMudhra revokes eight additional RSA certificate authorities

    eMudhra revoked six RSA TLS CAs and two RSA code-signing CAs that it had previously described as unaffected. It used the cessationOfOperation reason, prompting questions in Mozilla's bug thread about why keyCompromise was not used.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  8. Reported Nov 11, 20266d ago

    Further review establishes that the RSA CAs require revocation

    Following discussions with browser root programs, eMudhra concluded in early November that the eight RSA CAs required revocation. It could not demonstrate compliance with its HSM key-handling requirements because the ceremony computer's records did not reliably establish how exposed private material had been handled.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  9. Reported Nov 11, 20266d ago

    eMudhra announces exit from publicly trusted TLS issuance

    On October 22, eMudhra announced that it was leaving the publicly trusted TLS certificate business, requiring affected customers to migrate to another certificate authority. The company said its digital signature, eSign, and enterprise products remained unaffected.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  10. Reported Nov 11, 20266d ago

    eMudhra initially declares RSA issuers unaffected

    In an October 19 statement on Mozilla's bug tracker, eMudhra said its RSA issuers followed a different, unaffected code path. Subsequent investigation found that their private components had also been read into the ceremony computer's memory.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  11. Reported Nov 11, 20266d ago

    eMudhra revokes eight compromised ECDSA certificate authorities

    eMudhra revoked eight ECDSA CAs on October 18 using a CA-compromise revocation reason. Their private-key values had been reduced to a single byte by the transfer script.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  12. Reported Nov 11, 20266d ago

    Four affected RSA certificate authorities enter production

    eMudhra put four of the subsequently revoked RSA CAs into production in May. Its certificate inventory later identified 195 certificates issued under those CAs, including 29 for its own domains.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  13. Reported Nov 10, 20267d ago

    Electron application testing identifies potential malicious-update exposure

    A researcher reported lab findings that many Electron applications still trusted compromised eMudhra certificates and did not verify automatic-update signatures. The researcher claimed that the combination could allow a network-positioned attacker to install malware; the supplied excerpt identifies no affected applications or observed exploitation.

    Electron, we have a problem : r/netsec
  14. Nov 10, 20268d ago

    Microsoft announces removal of remaining eMudhra roots

    Microsoft announced the removal of the remaining eMudhra roots from Windows, Edge, and WebView2 in its November 10 update. The trust-store changes were scheduled to begin November 16.

    eMudhra Revokes 8 More Certificate Authorities Following Major SSL Private Key Security Failure | Cryptika Cybersecurity
  15. Reported Oct 30, 202619d ago

    Cloudflare reports forged eMudhra certificates and continued client trust

    Cloudflare reported certificates forged using the affected intermediates' weak keys and found that some sampled clients still accepted affected chains. The challenge-page sample was skewed toward bots, so the findings neither establish an Internet-wide patch rate nor demonstrate successful traffic interception.

    eMudhra certificate compromise | Zero Wire | Cloudflare Radar
  16. Oct 26, 202623d ago

    Microsoft releases emergency Windows updates to block affected eMudhra chains

    Microsoft released out-of-band Windows updates to remove trust in affected eMudhra certificate chains on systems unable to receive automatic certificate trust updates.

    eMudhra revokes 8 more CA certificates after private key mishap
  17. Jun 2025

    Invalid revocation-list signatures reveal an early symptom

    Invalid certificate revocation list signatures appeared in June 2025. eMudhra addressed the failures by re-signing the lists with the weak ECDSA keys matching the certified public keys, rather than detecting the underlying key-generation problem.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
  18. Apr 30, 20252y ago

    eMudhra key-transfer ceremony weakens ECDSA keys and exposes RSA key material

    During an April 30, 2025 ceremony involving 16 CA keys, eMudhra's Python transfer script read private keys into the ceremony computer's memory and truncated eight ECDSA private values to one byte. Eight RSA keys also passed through the read-back process, although their values were not shortened.

    eMudhra Revokes 8 More CAs It Previously Declared Unaffected by Key Compromise
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Organizations

2 linked
EmudhraeMudhra Limited

Breaches

3 linked
EMUDHRALIMITED-2025-04EMUDHRA-2025-04EMUDHRALIMITED-2026-11
Do you run this?See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
Check Your Exposure
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.