What Chrome’s Expected 27 October emSign Root Removal Means for Store Certificates

A browser verifies a checkout page’s TLS certificate through a chain. The store’s certificate is signed by an intermediate certificate authority, and that intermediate is signed by a root that the browser already trusts.

On 17 October 2026, a security researcher reported that the private keys of eight intermediate certificate authorities run by eMudhra, an Indian company that sells certificates under the emSign brand, could be computed from their public certificates. Chrome and Firefox blocked the affected certificates within hours. Chrome is expected to remove the root that signed them on 27 October, and some legitimate certificates that chain to that root will stop working in Chrome. For website operators, the practical question is whether their own certificate chains to that root.

What the Padlock Relies On at Checkout

The browser trusts a list of root certificate authorities. Chrome keeps its own list, called the Chrome Root Store. Mozilla maintains a trusted certificate list in NSS, which other applications use, and can also block individual intermediates through a centralized list of revoked certificates called OneCRL, which it says works without a user update or restart.

A certificate can stop working when a root in its chain is removed, as Google says will happen to some legitimate certificates chaining to emSign ECC Root CA – G3 in Chrome.

Chrome and Firefox used different mechanisms to block the affected intermediates, described below.

Blocking by Key
Google says Chrome blocked the affected intermediates by public key, so every certificate sharing those keys was covered. The block was in place on 17 October, before the root removal.

Eight Intermediates Blocked Within Hours on 17 October

Chrome received the report at 18:05 UTC on 17 October and deployed a block at 19:45 UTC. Google says Chrome blocked the intermediates by public key, so every certificate sharing those keys was covered. Mozilla received its report at 20:06 UTC and finished the OneCRL block for standard Firefox installs at 22:59 UTC.

The Hacker News says the eight intermediates are six TLS intermediates and two code-signing intermediates. It also says Chrome did not need to block the code-signing pair, because its verifier does not build a TLS path through an intermediate restricted to code signing.

Google says Android devices received an equivalent update through Google Play Services around 22:00 UTC on 19 October, and that the majority already had it. The Hacker News timeline lists Apple blocking the certificates on 19 October and Microsoft on 20 October.

The Hacker News says the keys did not have to be stolen. They were generated with too little randomness, so anyone can compute them from the public certificates. Google says no TLS certificates chaining to the affected intermediates were logged to Certificate Transparency before the block, so no fraudulent certificate from them could be used against clients that enforce Certificate Transparency.

Each of the eight also exists as a second certificate with the same public key, cross-signed by Sectigo under its AAA Certificate Services root, according to a list published by a Mozilla cryptography engineer and reported by The Hacker News. Chrome’s key-based block covers those copies too. Chrome and Firefox stopped trusting the AAA root for websites in April 2025, and Chrome’s root store does not include it. Apple’s root list for iOS 26 and macOS 26, published in December 2025, does include it.

On 20 October, Mozilla released Firefox 158.0.1 for desktop and Android, Firefox ESR 115.43.1 and ESR 153.5.1, and NSS 3.131.1, and removed the root that signed the affected intermediates. Google’s post names that root as emSign ECC Root CA – G3. Mozilla says the releases deliver this protection to a minority of users whose custom settings may have kept them from receiving the OneCRL update.

What eMudhra Says About the Keys and the Business

eMudhra says the eight intermediates were created under its ECC root in a key generation ceremony on 30 April 2025, using FIPS 140-2 Level 3 hardware security modules. It attributes the weak keys to a flaw in a key wrap and unwrap step, which produced a second, weak set of keys alongside the intended strong keys. Google says the keys were generated with weak entropy, meaning the randomness behind them was not strong enough. The root cause is still under investigation, according to The Hacker News.

According to The Hacker News, eMudhra says its infrastructure was not compromised and no data was breached. Its website statement of 20 October says the root keys and other intermediates are unaffected, only one of the eight intermediates was deployed in production, and none of the eight had issued an end-entity certificate. Google says some legitimate certificates chaining to the root will stop working in Chrome.

According to The Hacker News, eMudhra says its roots and issuing CAs passed independent audits two years running and have been in browser trust lists since mid-2025. It says the global TLS business is about 1% of its revenue, acknowledges a reputational risk it cannot quantify, and is issuing replacement certificates to affected customers. It also says the incident has no connection to its Indian digital signature and eSign businesses.

The same account reports that eMudhra’s shares fell 20% in Mumbai on 21 October, citing Business Standard.

Why the 27 October Removal Reaches Websites

27 October is the date Google gives for the removal. Google says the removal of emSign ECC Root CA – G3 is expected to reach devices that rely on the Chrome Root Store that day, Pacific time, and that prerelease channels such as Chrome Canary and Chrome Beta will get it sooner. A Chrome post on the Mozilla policy list said the removal would come in Chrome Root Store version 43 and gave no date. The Hacker News gives the same date, with arrival expected on the morning of 27 October, Pacific time.

Google also says that some legitimate certificates chaining to this root will stop working in Chrome. A website operator with such a certificate must install a new TLS certificate from another hierarchy in the Chrome Root Store before the removal. Google says eMudhra has committed to helping affected subscribers migrate. On the policy list, Mozilla said the NSS removal would affect the availability of some servers for non-Firefox users until they move to new certificate chains.

The removal concerns this root only, although Chrome is also reviewing eMudhra’s other root in its store, emSign Root CA – G1. A website operator whose certificate chain does not run through emSign ECC Root CA – G3 is not covered by this step.

Mozilla says the NSS update also helps protect other applications that use its trust store or derived versions and do not receive OneCRL updates.

A certificate can stop working when a root in its chain is removed.

How a Brand Can Check Its Own Store Certificate

Check the certification path for each checkout domain. If an entry names emSign ECC Root CA – G3, the store’s certificate chains to the root that Chrome is expected to remove.

Check every domain on the payment path. A chain that does not show that root is outside this removal.

The same public key can be cross-signed under more than one root, as with the Sectigo copies described above. For that reason, check the full path for each domain rather than the issuer name alone.

What to Ask an E-commerce Platform or Host Before 27 October

Ask which certificate authority issued the certificate for each checkout domain, and whether any chain passes through emSign ECC Root CA – G3. Ask for the date a replacement from another root in the Chrome Root Store will be installed, and who will do the installation.

Ask whether the replacement will cover custom domains and checkout subdomains, and how the switch will be tested before it goes live. If the store holds a certificate from eMudhra, ask what migration help the company offers, since Google says eMudhra has committed to working with impacted subscribers to migrate. Get the answers in writing with dates. A replacement that arrives after 27 October may leave certificates chaining to that root unable to work in Chrome.