Status as of 21 October 2026.
Eight intermediate certificate-authority keys controlled by eMudhra were found to be weak enough for outsiders to recover. These are keys used by certificate issuers, with consequences extending beyond an individual website. Mozilla's incident record.
For a website owner, there are two jobs to arrange: replace a website certificate if its chain is affected, and update the software that verifies HTTPS connections. Your hosting provider or developer should confirm the result for each. A website with an unaffected certificate can still run an API client that trusts the compromised authorities.
Which website certificates need replacing
Google says operators whose certificates chain to emSign ECC Root CA – G3 should immediately install a certificate under another trusted hierarchy. Chrome's wider root-removal rollout is expected on the morning of 27 October 2026, Pacific Daylight Time; prerelease channels can apply it sooner. Other software is also receiving trust changes, so arrange replacement now. Google's advisory.
Check the full certificate chain, including its root. The certificate's expiry date or immediate issuer name alone does not answer this question. Ask the provider issuing your replacement to confirm that the new chain ends at an accepted root. A replacement from the same supplier can be suitable if it uses a different trusted hierarchy.
An existing, legitimately issued certificate can stop working when its root loses trust. There is no need to replace every website certificate indiscriminately; identify which deployed chains require migration.
Check the public website and its origin
Start with your hosting control panel or your provider's certificate-management service. Browser certificate details can help inspect a public connection, but ask the provider to verify the deployed chain where the browser interface does not show enough information.
Include the main domain, www, shop and customer-portal subdomains. If a CDN or reverse proxy sits in front of the site, check its public certificate and the separate certificate used between that service and your origin server. A working public homepage does not verify every connection behind it. Cloudflare specifically asks customers to review custom origin certificates and TLS configurations. Cloudflare's guidance.
You can send the responsible provider this request:
Please check the complete TLS certificate chains for my domains, including any CDN and origin connections. Does any deployed chain reach emSign ECC Root CA – G3? If so, please replace it under a currently trusted hierarchy and confirm the new chain. Please also confirm that the server software making outgoing HTTPS requests has received the relevant trust-store updates.
Update software that verifies HTTPS
Your server also acts as an HTTPS client when it contacts payment services, delivery systems, external APIs or update servers. Establish where each application gets its trusted certificates. For example, curl can use a native system store or a separate CA file, depending on its build and configuration. curl's certificate documentation.
| What needs checking | Work to arrange |
|---|---|
| Website and origin certificates | Replace affected chains and verify the deployed replacement. |
| Server applications and background jobs | Apply the supplier's trust-store or dependency fixes and restart or redeploy where required. |
| Containers and locally managed tools | Update affected base images and packages, rebuild and redeploy. |
Ask your developer to identify the verifier actually used by each important integration. An operating-system update may leave an application's bundled certificate store unchanged. For Cloudflare Tunnel users, Cloudflare lists cloudflared 2026.10.2 as its corrected release; container deployments need the updated image deployed too. Follow the vendor's current guidance for other clients. Cloudflare's update instructions.
There are also alternate certificate chains involving Sectigo cross-signs. Administrators should use the relevant vendor fixes covering those paths. Deleting one root manually is not a reliable substitute for checking the application's complete trust policy. Mozilla's incident record.
Keep browsers and devices updated
Browser vendors distributed emergency blocks. Mozilla's 21 October update also announces Firefox for Android 158.0.2, addressing some clients not applying the bundled blocklist immediately after startup. Install the latest supported browser and operating-system updates, rather than assuming an earlier emergency release settled every case. Mozilla's advisory.
The technical incident tracker provides browser checks and information about corrected software packages. A result describes the client being tested. Passing in your browser does not verify a shop's payment integration, a scheduled import or another application on the same computer.
Why the compromised keys matter
A certificate authority helps a client decide whether a server is entitled to represent a domain. A forged certificate can make an impersonated service appear legitimate to a client that still accepts the affected authority. An attacker able to intercept the connection could then read or alter traffic. The failure concerns authentication through certificates, rather than a break in TLS's encryption algorithms. Mozilla's explanation, Cloudflare's explanation.
Google's assessment of protection before the emergency block applies to clients enforcing Certificate Transparency. It does not establish that every non-browser application was protected. Cloudflare says its review found no active exploitation on its services; that finding has the same limited scope. Google's advisory, Cloudflare's report.
Verify the work and keep certificate checks enabled
Ask for a record of the certificate chains checked, replacements installed, software packages updated and services restarted. Confirm that important pages work, then test the affected integrations through their actual application path. For a shop, use the payment provider's test environment where available.
If updates expose certificate errors, investigate the rejected chain and the service presenting it. Keep certificate verification enabled. Bypassing it would remove the identity check the remediation is meant to restore. curl's guidance on certificate verification.
The same maintenance discussion should identify who handles future certificate renewals and security updates. For the separate PHP incident, see the fixed PHP versions and checks for website owners.