Microsoft Rushes Emergency Windows Patch After Indian Certificate Authority's Signing Keys Prove Trivially Guessable

Microsoft pushed an emergency, out-of-band update to Windows on October 26 to strip trust from seven certificates tied to eMudhra, an Indian certificate authority, after security researchers showed that eight of the company's intermediate signing keys were so weak they could be reconstructed from public information in under a second. Microsoft said it would remove the same certificates from Microsoft Edge's trust list on October 27, following similar emergency moves already taken by Apple, Google and Mozilla.

The flaw strikes at one of the internet's most basic assumptions: that a padlock in the browser means a site's identity has been verified by an authority nobody else can impersonate. eMudhra's role as a certificate authority meant its signing keys were supposed to be unguessable, large random numbers roughly 116 digits long. Instead, researchers found that eight of its intermediate keys, generated during an April 2025 signing ceremony, were integers smaller than 256 — meaning anyone willing to try at most 256 guesses could recover them.

A Key Weak Enough to Guess

According to Microsoft's own account of the incident, posted to its Security Response Center blog, six of the eight compromised intermediates were used to issue TLS certificates for websites and two were used for code signing. On October 20, Microsoft added the affected certificate authorities to the Windows Disallowed Certificate Trust List and pushed a CRLSet update blocking the TLS certificates in Edge and WebView2. That was followed by the October 26 out-of-band update for Windows 11 and a parallel update for Windows 10, which together remove seven certificates outright: six eMudhra "G3" root certificates and one older AAA Certificate Services cross-sign used to help those roots validate on older systems.

Security researcher Scott Helme, one of several people who independently verified the flaw after it was first reported by a researcher using the handle "Wayne," described how little effort recovery took.

"I recovered all of them from their public certificates on my laptop just now, and it took less than a second."

Helme also noted that one of the eight private key values was simply the number four. Normally, he said, a compromised certificate-authority key implies that someone stole it; in this case, the key had effectively been public since the moment the certificate was issued, because it could be derived from information anyone could already see.

How a Signing Ceremony Went Wrong

Certificate authorities like eMudhra operate under strict audit regimes — including the WebTrust program run by independent accounting firms — precisely because browsers and operating systems extend blanket trust to whatever the CA signs. eMudhra has said a script deployed during its April 2025 key-generation ceremony produced a second, much weaker set of keys alongside the properly generated ones, and that staff mistakenly used the weak keys when preparing some certificates because their internal labels closely resembled those of the correct keys. The company disclosed the compromise in a filing on the National Stock Exchange of India after the flaw surfaced, and said it would exit the global SSL/TLS certificate business, which it described as roughly 1 percent of its revenue, while maintaining that its domestic digital-signature and eSign operations were unaffected and that no customer data was exposed.

Microsoft, in its advisory, drew a careful distinction between the different layers of the response: eMudhra's own revocation of the eight compromised intermediates, browser-makers' separate decisions to block those intermediates outright, and the broader step — which Microsoft and others ultimately took — of pulling trust from the root certificates that anchor eMudhra's entire certificate hierarchy, not just the compromised branches. "Removing a root from a trust list is not the same as revoking the known impacted intermediate certificate authorities," the company said, adding that it is still evaluating eMudhra's remaining roots and may make further trust changes as customers migrate away from them.

Who Is Affected

For most internet users, the practical exposure is limited: browsers and operating systems update their trust lists automatically, and no browser maker has reported evidence that the weak keys were exploited to forge a certificate for a real website before they were revoked. The greater disruption falls on organizations whose websites, code-signing pipelines or internal systems rely on certificates that chain up to the affected eMudhra roots — Microsoft is urging administrators to identify any such certificates and replace them before the trust changes reach their devices, and it flagged particular risk for Windows systems that are offline or otherwise cut off from automatic certificate-trust updates, including disconnected Azure virtual machines.

In India, where eMudhra is based and publicly traded, the fallout has been immediate and financial: the company's shares fell sharply over multiple trading sessions after the disclosure. India's Ministry of Electronics and Information Technology said it had formed a special team to investigate the incident and was coordinating with eMudhra and other stakeholders, while stating that the impact on Indian websites and applications had been "very limited and for a very short duration" because the compromised keys belonged to eMudhra's international public-key infrastructure business rather than the domestic Digital Signature Certificate and eSign services the ministry regulates. India's computer emergency response team, CERT-In, also issued an advisory recommending that organizations update browsers and trust stores, audit services tied to the affected certificates, and watch for signs of unauthorized certificate issuance.

What Happens Next

Microsoft said it would continue investigating the scope of the eMudhra compromise and would update its advisory if further findings require additional trust changes, suggesting the response is not yet finished. The company said organizations with a specific compatibility need could choose to trust an affected certificate locally, but only after completing their own risk assessment, underscoring that the broader removal of trust is deliberately blunt. For eMudhra, the episode marks a retreat from a business line it has said it will exit entirely, even as it continues to insist that the root cause was a flawed key-generation process rather than a network intrusion. Investigators in India and the independent auditors who oversee eMudhra's WebTrust certification are expected to produce more detailed findings on how a four-digit-or-smaller number ended up anchoring trust for part of the web.