Why it matters
Operators should apply updates or follow platform guidance to block the compromised certificates; systems that still trust them may accept forged website or client-auth certificates.
What we know
Confirmed by several sources
Reported by one source
- The keys were exposed because of low entropy, rather than a known breach. — InfoQ
- The compromise could also enable forged client-authentication and mTLS certificates. — InfoQ
- Chrome blocked the certificates on October 17, Apple devices on October 19, and Microsoft on October 20. — LWN.net
- NetBSD published instructions to block the certificates. — LWN.net
Open questions
- Whether other browsers and operating systems have blocked the certificates or issued guidance remains unclear. — LWN.net
Coverage 3 publishers
LWN.netFirst report
eMudhra intermediate CA compromise
Mozilla has announced that it has received a report that private keys associated with eight eMudhra intermediate certificates have been compromised: These keys could allow attackers to issue fraudulent HTTPS certificates for websites they…
-
Your MCU Likely Escaped the eMudhra Intermediate CA Compromise
If you are a software engineer, or generally work in the tech industry, there is a good chance that you heard about the eMudhra Intermediate CA Compromise that was disclosed yesterday (October 20, 2026). If you don’t, you may have noticed…
-
eMudhra Intermediate CA Compromise
Private keys for eight eMudhra intermediate CA certificates have been compromised, allowing attackers to forge certificates for any site. The keys were revealed due to low entropy, not through a known breach. Browsers blocked them using…
Earliest report first. Articles stay on their publishers’ sites; each link opens the original.
