🔒eMudhra Intermediate CA Compromise Affects 8 Certificates
8 Certificates Compromised, Keys Were Shockingly Weak
TL;DR
eMudhra's intermediate CA compromise affects 8 certificates with extremely weak keys. The top 376 bits of P-384 keys were all zeroes, impacting software establishing TLS connections.
eMudhra's intermediate CA compromise was disclosed on October 20, 2026, affecting eight certificates with shockingly weak private keys. The top 376 bits of P-384 keys were all zeroes, with one key literally being the number 4. This compromise led to widespread software updates for establishing TLS connections. MCUs are unlikely to be impacted due to resource constraints, while desktop/server machines see minimal impact. The root CA certificate for google.com remains unaffected, but the disclosure highlights critical security flaws in certificate management.
Key Points
eMudhra Intermediate CA Compromise disclosed on October 20, 2026.
Compromised certificates created in April 2025, no logs in certificate transparency.
Top 376 bits of P-384 keys were all zeroes, one key literally the number 4.
MCUs unlikely to be impacted due to resource constraints, <1 MB non-volatile storage.
Root CA certificate for google.com remains unaffected, trust chain intact.
Why It Matters
If you're managing TLS connections, the eMudhra compromise means you need to update software to ensure secure connections. The weak keys highlight critical security flaws in certificate management, impacting workflows that rely on robust TLS setups. Desktop/server machines see minimal impact, but the disclosure underscores the importance of vigilant security practices.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,569 builders reading daily.