By Darren Meyer, Research Advocate, Checkmarx
Browser maintainers acted within hours of the eMudhra report. That is the good news, but it could lead some security teams to wrongly consider the matter closed.
What happened
On October 17, a researcher using the handle “Wayne” reported to the browser root programs that the private keys of eight eMudhra intermediate CA certificates had been compromised, and proved it by signing messages with each key. According to Google, the cause was weak entropy at generation. Every affected key was just one byte. Anyone could recover a private key from the public CA certificate by generating the first 256 P-384 keys and comparing. That meant anyone could forge HTTPS certificates for any website or application; clients that still trusted these CAs would accept them.
eMudhra says the problem is confined to eight intermediates from an April 2025 key ceremony and that none issued an end-entity certificate. On October 22, it announced it will exit the SSL/TLS certificate business.
Google found no TLS certificates chaining to the six TLS intermediates in Certificate Transparency (CT) logs. That protected browsers enforcing CT, but many developer tools and servers don’t, so it isn’t known whether any were targeted.
Patching the browser is not patching the estate
Chrome, Firefox, Apple and Microsoft all blocked the intermediates within days. But browsers are only the beginning. Runtimes, package managers, containers, command-line tools and operating systems make their own trust decisions, each with its own trust store and update cycle.
Go shows why this matters. It doesn’t check for revocation, so its fix only works once an application is rebuilt and redeployed on a patched release. Binaries already in production stay exposed. Go 1.25 and older get no fix at all, so those teams must move to a newer release.
Other layers have gaps of their own. Apple’s built-in curl relies on a certificate file that hadn’t been updated when the incident went public. Edge on Windows 10 was reportedly still connecting to test hosts as Microsoft rolled out its fix, and that block depends on automatic root updates, which locked-down or offline environments may not receive. Two of the eight are code-signing intermediates, so signed software could look legitimate to tools that skip revocation checks.
My view: trust is a dependency, and most of us don’t inventory it
Supply chain security programs have matured around code, packages and build pipelines. This incident shows how little of that maturity extends to the trust layer beneath them. Every layer of your stack inherits trust decisions made elsewhere, and if one layer still trusts a compromised CA, forged certificates can get through. A patched browser on the CISO’s laptop tells you nothing about the service in your fleet running an old binary.
What security teams should do now
1. Find every trust store you own. Check runtimes, base images, containers, command-line tools, package managers and internal services that ship their own CA bundles.
2. Confirm nothing chains through the eight intermediates. A forged certificate looks valid to any client that still trusts the chain. Mozilla’s Dennis Jackson runs a public incident site with client checks, machine-readable lists of the intermediates and a table of patched versions.
3. Rebuild and redeploy Go services. Move to a supported patched release (1.27.3 or 1.26.10). A patched toolchain on a build server offers incomplete protection until the rebuilt application is running in production.
4. Check offline and locked-down environments, where automatic trust updates are most likely to be switched off.
5. Plan for breakage. Go blocks the eight keys, but Python’s certifi and Rust’s webpki-roots removed the whole root, which cuts off legitimate certificates beneath it. The Go filter has no off switch and likely affects private deployments that deliberately trust one of these keys. Test first, and tell your application owners what to expect.
6. Make trust updates routine. Treat CA bundles as versioned dependencies, tracked in your inventory like any other component.
The lesson
This incident was caught quickly, and the exposure that remains sits in places we rarely look. Supply chain security has to cover the trust layer that every component relies on.