Article title: India's eMudhra Certificate Security Incident Follow-up: Microsoft Further Blocks 10 Root Certificates, Offline Windows Devices Need to Deploy Subsequent Update Packages
Body:
- Day/Night Follow System Light Dark
India's eMudhra Certificate Security Incident Follow-up: Microsoft Further Blocks 10 Root Certificates, Offline Windows Devices Need to Deploy Subsequent Update Packages
IT之家 November 16 news, Microsoft will further remove the default trust of the remaining 10 root certificates of Indian digital certificate authority eMudhra in Microsoft products and services starting November 16. This means that certificate chains issued using the relevant root certificates will no longer be trusted by default, and websites, services, and software that rely on these certificates may experience certificate verification failures, and users will be unable to access or use the relevant services normally.
According to information published by the Microsoft Security Response Center (MSRC), Windows will remove the remaining 10 eMudhra root certificates from the trusted root certificate list through the automatic certificate trust update mechanism.
Windows devices that can connect to Microsoft's certificate update service will automatically receive this adjustment, without the need for users to manually download or install updates. Microsoft states that the relevant changes also apply to Windows devices in Azure environments.
Microsoft Edge browser and WebView2 Runtime also removed default trust in the remaining relevant root certificates on November 16 through a PKI Metadata component update. Devices typically check for PKI Metadata updates every 10 hours and also proactively check after an application starts, so users do not need to wait for a new full browser version release.
This adjustment is a further measure taken by Microsoft in response to the eMudhra certificate security incident. Previously, 8 intermediate certificate authority (CA) private keys of eMudhra could be derived due to problems in the generation process, of which 6 were used for TLS website certificates and the other 2 were used for code signing certificates.
Microsoft points out that attackers who possess these private keys could use them to issue seemingly trusted certificates and impersonate legitimate websites or software publishers. Using the relevant TLS private keys, attackers could impersonate legitimate websites and intercept user communications; using the code signing private keys, they could make malware appear to be published by trusted software vendors.
Microsoft emphasizes that this issue originated from eMudhra's certificate system, and that Microsoft's own systems were not compromised.
Regarding the 8 confirmed affected intermediate certificates, Microsoft had already released an update through the Windows Disallowed Certificate Trust List on October 20, 2026, placing the relevant certificates within the blocking scope. Microsoft Edge and WebView2 also blocked affected TLS certificates issued by these intermediate certificates through an independent CRLSet component update.
On October 26, Microsoft further removed 7 relevant certificates from the Windows trusted certificate list, including 6 eMudhra G3 root certificates and 1 AAA Certificate Services cross-signed certificate. On October 27, Edge also completed the corresponding adjustment.
The operation on November 16 targets the remaining 10 eMudhra root certificates, further expanding the scope of certificates no longer trusted. Microsoft states that removing root certificates from the trust list and blocking intermediate certificates that have been confirmed to have private key risks are security measures at different levels. Even if a certain root certificate itself has not been confirmed to have a private key leak, Microsoft can still stop trusting the relevant certificate system for overall security considerations.
For websites, services, and software that still use eMudhra certificates, Microsoft recommends checking the certificate chain as soon as possible and replacing them with certificates issued by other trusted certificate authorities, to avoid connection failures or software signature verification anomalies after the relevant trust changes take effect.
For Windows devices that have been offline for a long time and cannot connect to Microsoft's certificate update servers, Microsoft had previously provided handling measures for the 7 certificates removed in October through out-of-band updates and the November 10, 2026 security update. As for the change on November 16 to remove the remaining 10 root certificates, Microsoft states that a separate offline certificate update solution will be provided, and IT administrators will need to manually download the update package and deploy it to the relevant devices.
Microsoft also reminds enterprise administrators not to re-trust certificate systems that have already been removed through local configuration without completing a security assessment, otherwise the relevant malicious certificates may still be accepted by some software that cannot correctly check certificate revocation status.
Related Articles
- Microsoft lobbies the U.S. government to abandon import restrictions on Chinese optical modules, concerned about slowing AI data center construction
- Microsoft: Continuously optimizing Win11 memory usage, 8GB RAM models in 26H2 version can "match" 2021 16GB RAM machines in specific scenarios
- Some GPU computing contracts delayed, Microsoft lowers 2026 capital expenditure forecast to 170 billion USD
- Microsoft FY2027 Q1 revenue 92.279 billion USD, up 19% year-over-year, net profit attributable to parent 36.629 billion USD, up 32% year-over-year
- Microsoft launches voluntary departure buyout program for about 60,000 employees, adapting to AI-era personnel structure adjustments
- India's eMudhra announces exit from global SSL / TLS certificate business, admits flaws in key generation process and human error
Websites under Soft Media: IT之家 最会买 - 返利返现优惠券 iPhone之家 Win7之家 Win10之家 Win11之家
Software under Soft Media: 软媒手机APP应用 魔方 最会买 要知