Eight intermediate TLS certificates from eMudhra with private key sizes of just 3 to 8 bits were compromised; browser makers and major apps have blocked them
Security personnel around the world are on high alert Tuesday following the discovery of eight TLS certificates with private keys …
The eMudhra incident tests that containment path at the intermediate-certificate layer. Its same-day coverage by Mozilla, security researchers, and eMudhra itself underscores that the affected certificates sit inside trust chains used well beyond a single vendor’s own software.
First-order effects
Browsers and major applications that block the eight intermediates will reject certificate chains relying on them, requiring affected eMudhra TLS customers to move to replacement chains to avoid connection failures.
eMudhra’s investigation is focused on a portion of its TLS-certificate customers; the company says its enterprise applications and digital-signature service are unaffected.
Second-order effects
The emergency blocks create uneven protection: Scott Helme warned that mainstream browsers may be protected while a long tail of software with slower trust-store updates remains exposed to the compromised intermediates.
Organizations using eMudhra-issued TLS certificates must validate their deployed chains across browsers, operating systems, and embedded clients, turning a CA incident into an operational migration task for customers.
Third-order effects
The incident reinforces that browser and operating-system trust stores are a de facto control plane for the web: they can rapidly isolate a failing intermediary, but the protection depends on every client receiving the policy change.
If weak-key issuance is not caught before deployment, CA security will be judged not only on cryptography but on whether issuance controls, audits, and revocation mechanisms work across the full software ecosystem.
The trend: Web trust is becoming more dependent on rapidly coordinated trust-store enforcement as certificate-authority failures propagate across interoperable clients.
Firefox 158.0.1 Is Out to Block Compromised eMudhra Intermediate Certificates
@scott_helme
Scott Helme on x
Damn, this is really bad. Mainstream browsers will probably be fine, but there is a long tail of other stuff that will be affected by this: https://scotthelme.co.uk/...
@emudhra
@emudhra on x
eMudhra is investigating a security incident affecting a portion of our TLS certificate customers. This incident has no impact on customers using our enterprise applications, digital signature services, or other electronic signature solutions. We are actively engaging with affect…
@ghidraninja
@ghidraninja on x
So the private-key for the eMudhra (revoked) intermediate was apparently 4. How is the root still trusted? How broken are your processes if this can happen? And honestly: How have we (as an industry) not noticed earlier :(
@jedisct1
Frank on x
The private keys of eight eMudhra intermediate CA certificates have been compromised. They chain to roots trusted by the Mozilla, Microsoft, Apple and Chrome root programs and by many downstream trust stores. https://emudhra.we-have-a-problem.com/
@logic
@logic on x
This may be the first major CA incident both discovered by an AI agent (the reporter Wayne's discovery path hints at it) and confirmed via agents recovering keys with a single prompt. Global shame - @eMudhra
@astuyve
AJ Stuyvenberg on x
more answers here https://bugzilla.mozilla.org/ ...
@charliermarsh
Charlie Marsh on x
We just released uv 0.13.4, which updates our bundled certs in response to the eMudra incident. This is a huge deal, and not unique to uv! It affects much of open source due to bundled CAs in certifi, webpki-root-certs, etc. Please upgrade anything that bundles CA certs.
@iangcarroll
Ian Carroll on x
It appears these intermediary certificates were issued with single-byte P-384 private keys. This means anyone can exploit this issue locally and issue valid certificates under them with no effort. This is very, very bad! Seems undetected since issuance in 2025?
@astuyve
AJ Stuyvenberg on x
private keys from 8 intermediate CA certs have been compromised (eMudhra) Happy “Update everything” day to all my pager-carrying friends https://emudhra.we-have-a-problem.com/
@geoffreyhuntley
Geoff on x
idk if you saw but eMudhra CA got popped. big deal folks. https://emudhra.we-have-a-problem.com/ Have monkey-patched https://overalls.dev/ and found a new cute trick. My new favorite prompt follows: >
@iangcarroll
Ian Carroll on x
For the next few days or weeks, anyone now has a root CA thanks to eMudhra. Time to have some fun with MiTMing unwilling devices!
@malwarejake
Jake Williams on bluesky
I had to read the sentence “Astonishingly, the private keys were 4, 56, 66, 115, 155, 156, 230, 237” several times, because despite knowing @dangoodin.bsky.social superior attention to detail, my brain was *certain* that could not be correct. [embedded post]
r/technology
r on reddit
Protecting Firefox users following the compromise of eMudhra intermediate certificates - Mozilla Security Blog
@molly.wiki
Molly White on bluesky
“The compromised eMudhra keys were defective at a level that's challenging the imagination of many of the engineers studying the incident. ... ‘That is extremely in the ‘this should not be possible’ category,’ Valdorda said.” [embedded post]
r/cybersecurity
r on reddit
The Internet goes on high alert after discovery of 8 compromised TLS certs