Following the compromise of eMudhra certificate authority private keys, Microsoft released an out-of-band update removing seven eMudhra G3 root certificates from Windows and Edge trust lists. Isolated environments require manual installation.
Key points
- What happened: Six eMudhra G3 root certificates and one Sectigo cross-signature were removed from Windows and Edge trust lists
- Why it matters: Blocking individual intermediate CAs alone leaves a path for software without revocation checks to accept compromised certificates
- For isolated-environment administrators: Devices unable to receive automatic CTL updates need manual installation of KB5134133 or KB5134125 and an inventory of certificates depending on the seven removed entries
eMudhra G3 root certificates removed from trust lists
On October 26 local time, Microsoft released an out-of-band (OOB) cumulative Windows update. It removes seven certificates from Windows trust lists: six eMudhra G3 root certificates and one AAA Certificate Services cross-signature issued by Sectigo. The same seven were removed from Edge's trust list on October 27.
Joho no Todai confirmed that the Microsoft Security Response Center (MSRC) blog documents the response and lists the removed certificates.
On October 20, Microsoft had already blocked eight problematic intermediate CAs by adding them to the Windows Disallowed Certificate List. It also distributed CRLSet updates, browser revocation-information lists, for Edge and WebView2, the component that embeds Edge's rendering engine in other applications. These blocks applied without manual browser updates.
The OOB update goes further. Rather than individually blocking intermediate CAs, it removes the root certificates linking to them from the trust list itself.
Removing root certificates from a trust list differs from revoking the intermediate CAs where problems were found. This is a broader trust decision than blocking compromised intermediate keys. Organizations with compatibility requirements can also configure trust locally based on their own security assessments and policies.
Microsoft explains that software that does not reliably check revocation may still consider certificates from blocked intermediate CAs valid if their roots remain trusted. Removing those roots aims to close that path.
Private keys recoverable from 256 possible numbers
The incident began on October 17 local time, when security researcher Wayne discovered a critical flaw in the private keys of eight eMudhra intermediate CAs while scanning public certificate data. All eight had been generated in April 2025 using the P-384 elliptic curve, but their private-key values were integers below 256.
According to Mozilla's incident report, P-384 private keys should be randomly selected from an enormous range of integers. A value below 256 means all but the final byte are zero. Trying only 256 numbers suffices to recover a key; Mozilla cryptography engineer Dennis Jackson also reported independently recovering the keys.
Six intermediate CAs were for TLS, which encrypts communications, and two for code signing, which authenticates software publishers. Recovered TLS keys could enable impersonation of legitimate websites and interception of encrypted traffic. Code-signing keys could put trusted-publisher signatures on malware.
In its response to Mozilla, eMudhra said a script error during April 2025 key generation produced weak keys separately, which were mistakenly selected because their labels resembled those of legitimate keys. On October 22, it announced its withdrawal from the global SSL/TLS certificate business (in Japanese).
Who needs KB5134133 and what administrators should do
The OOB update targets devices unable to receive automatic certificate trust list (CTL) updates: disconnected devices in isolated environments, devices unable to access Microsoft's certificate update service, and devices with automatic CTL updates disabled.
In ordinary environments with automatic CTL updates enabled, the root removals have already been delivered automatically, and the additional OOB update is unnecessary.
KB5134133 covers Windows 11 24H2/25H2/26H2, while KB5134125 covers Windows 10 21H2/22H2. Both are available from the Microsoft Update Catalog.
Microsoft asks administrators to identify certificates depending on the seven removed roots and arrange replacement certificates or alternative trust paths. Restoring local trust for compatibility requires assessing the risk that software without revocation checks could accept certificates from compromised intermediate CAs through that path.
Microsoft is separately evaluating the remaining eMudhra roots and says further trust changes may follow as affected users migrate. The eMudhra key compromise (in Japanese) also affects certificate stores in language runtimes such as Go, Python, Node.js, and Electron, beyond browsers and operating systems, with projects responding individually. An incident tracking site published by a Mozilla cryptography engineer tracks responses by software product.
Originally published on Joho no Todai. The Japanese original is here.
Top comments (0)