MANILA, PHILIPPINES — November 2026 — A digital certificate can remain within its validity period and still lose the trust required for it to function as expected. This is the situation organizations may face following Microsoft's decision to remove the remaining eMudhra root certificates from its trusted root lists, beginning November 16, 2026.
The decision follows the discovery of compromised private keys associated with eight eMudhra intermediate Certificate Authority (CA) certificates in October. As part of its response, Microsoft is removing the remaining ten eMudhra root certificates across affected products and services. Once these changes reach a device or service, certificates that rely on the affected roots may no longer be trusted by default.
Understanding the eMudhra Certificate Incident
In October 2026, a security researcher identified recoverable private keys associated with eight eMudhra emSign G3 intermediate CA certificates: six used for Transport Layer Security (TLS) and two for code signing.
The weakness resulted from insufficient randomness during key generation, making the private keys recoverable from their corresponding public certificates. If obtained by an unauthorized party, these keys could potentially be used to issue fraudulent certificates or sign content that appears to come from a trusted source.
Following the discovery, eMudhra revoked the eight affected intermediate certificates on October 18. Microsoft and other browser and platform providers subsequently introduced measures to block the affected certificate hierarchies.
On November 12, Microsoft announced a further step: removing its remaining ten eMudhra root certificates from its trusted root lists, with changes beginning November 16, 2026.
It is important to distinguish the affected certificate authorities from eMudhra's broader services. According to CERT-In, the incident concerns its publicly trusted digital certificate operations. Its domestic digital signature certificate and eSign infrastructure, which operate using separate cryptographic keys and infrastructure, were not affected.
Sources: Microsoft Security Response Center | CERT-In Advisory: Compromise of eMudhra Intermediate CA Certificates
Why Certificate Trust Matters to Organizations
Digital certificates help establish trust between websites, applications, servers, and users. They support encrypted communications, authenticate digital identities, and help verify the integrity and origin of software.
When a root certificate is removed from a platform's trusted certificate store, certificates that depend on that root may no longer pass validation by default. Depending on the certificate chain and the platform involved, this can affect:
· Website and browser connections. Users may encounter certificate warnings or failed connections when accessing websites whose certificates rely on an affected trust chain.
· Application and API connectivity. Applications, APIs, and integrations may reject certificates they can no longer validate, potentially interrupting communications between systems.
· Authentication and secure communications. Services that depend on affected certificate chains may experience trust or connection failures.
· Code-signing validation. Software signed through affected certificate hierarchies may encounter verification or trust issues on platforms that no longer recognize those certificates.
The actual impact depends on the certificate hierarchy, the platform's trust store, and whether an alternative trusted certification path is available. Microsoft's changes are also being rolled out at different times across its products and services.
Source: Microsoft's Response to Compromised eMudhra Certificate Authority Keys
Could Your Organization Be Affected?
Organizations using eMudhra or emSign-issued certificates should reviewtheir certificate dependencies rather than relying solely on expiration dates.
The review should extend beyond public-facing websites. Certificates may also be used across internal applications, servers, network infrastructure, cloud environments, software deployments, and third-party integrations.
Particular attention should be given to systems that maintain their own certificate stores or do not automatically receive platform trust updates. Disconnected devices, containers, embedded systems, and applications with bundled certificate authorities may require separate assessment.
Organizations should also determine whether affected certificates have an alternative trusted certification path. The removal of a root certificate does not necessarily mean every certificate associated with that authority will fail validation across all platforms.
What Organizations Should Do
Organizations should take the following steps to assess potential exposureand prepare for certificate trust changes:
1. Review certificate inventories. Identify certificates issued under eMudhra and emSign hierarchies. Examine the complete certificate chain, including intermediate and root certificates.
2. Identify affected dependencies. Determine which systems, applications, and services rely on the affected roots. Coordinate with application owners, infrastructure teams, and third-party providers to establish potential operational impact.
3. Arrange certificate replacements where necessary. Work with the relevant Certificate Authority or certificate provider to obtain replacement certificates that chain to currently trusted roots. Plan the transition before affected certificates lose their default trust.
4. Test applications and integrations. Validate certificate chains and test websites, APIs, applications, and integrations after certificate replacements or trust-store changes.
5. Keep security and trust-store updates current. Ensure Windows, Microsoft Edge, and other affected platforms receive the relevant updates. Pay particular attention to disconnected devices and applications within dependently maintained certificate stores.
6. Avoid restoring trust without proper assessment. Do not reintroduce removed root certificates or bypass certificate validation simply to resolve compatibility issues. Any exception should undergo a documented security assessment and receive appropriate approval.
Organizations should refer to Microsoft's Trusted Root Program announcements and its response to the eMudhra certificate incident for the affected certificate list, platform updates, and customer guidance.
Certificate Trust Is an Ongoing Security Responsibility
The eMudhra incident highlights an important aspect of digital certificate management: validity and trust are not the same. A certificate may not have expired, yet changes in the trust status of its issuing hierarchy can affect whether systems continue to recognize it.
For organizations that rely on certificates to secure websites, applications, communications, and digital transactions, certificate management must extend beyond routine renewals. Maintaining visibility over certificate inventories, dependencies, expiration dates, and trust status is essential to reducing the risk of unexpected service disruptions.
Organizations should consider a broader approach to Certificate Lifeycle Management (CLM), ensuring that certificates are continuously monitored, properly maintained, and replaced when trust requirements change.
Netrust Philippines supports organizations in strengthening digital trust through cybersecurity services and solutions that help protect their digital environments and maintain secure, reliable operations.





