# eMudhra Certificate Compromise: Chrome Drops Its Root on Oct. 27

- URL: https://usa-24.com/emudhra-certificate-compromise/
- Publisher: USA 24
- Section: Cybersecurity
- Published: 2026-10-26T16:50:23.258Z
- Updated: 2026-10-26T16:50:23.270Z
- Topics: Certificate Authorities, SSL/TLS Certificates, Browser Security, Google Chrome, Supply Chain Security

> Chrome stops trusting an eMudhra root on October 27 after eight weak intermediate CA keys were cracked, and eMudhra is leaving global SSL/TLS. Here is what to check now.

## Key takeaways

- A researcher identified as Wayne reported eight compromised eMudhra intermediate CA private keys to Mozilla and Google on October 17, 2026.
- Six of the eight compromised intermediates issued website TLS certificates, and two were code-signing intermediates.
- Chrome will stop trusting emSign ECC Root CA – G3 on the morning of October 27, Pacific time.
- eMudhra says SSL/TLS is about 1% of its revenue and will replace affected customers' certificates free through partners.
- Servers, CI pipelines and command-line tools such as curl and git need updated CA bundles because many do not check revocation.

Chrome will stop trusting one of eMudhra's root certificates tomorrow, and the Indian certificate authority is leaving the global SSL/TLS business. The cause is a simple and damaging failure: eight of its intermediate signing keys were weak enough for a researcher to recover, and browsers blocked them within three days.

The eMudhra certificate compromise started with a private report on October 17. The developments that matter this week are eMudhra's [October 22 exit announcement](https://emudhra.com/en/press-release/emudhra-to-exit-global-ssl-tls-certificate-business) and Chrome's root removal, which reaches users on the morning of October 27, Pacific time.

## How the eMudhra certificate compromise unfolded

A researcher identified as Wayne reported that eight eMudhra intermediate certificate authority private keys had been compromised. [Mozilla's bug record](https://bugzilla.mozilla.org/show_bug.cgi?id=2083449) shows the report arriving at 20:06 UTC on October 17. Wayne proved control of each key by signing a message with it, and Mozilla independently recovered the same keys without knowing his method.

Mozilla moved first. It blocked the certificates in Firefox through its OneCRL list, and the rollout was complete by 22:59 UTC that day. Chrome blocked them on October 17 as well, Apple followed on October 19 and Microsoft on October 20.

eMudhra then explained the flaw. On October 21 it said a defect in an April 2025 key ceremony produced a second, weak set of keys, and that the weak set is what was published to root stores. Cloudflare's engineering team put the stakes plainly in [its blog post](https://blog.cloudflare.com/emudhra-certificate-compromise/): “This is a serious security incident with implications across the Internet.”

## Which certificates, versions and dates matter

Six of the eight compromised intermediates issued certificates for websites, and two were code-signing intermediates. A community summary lists the website group as domain validation, organization validation and extended validation TLS intermediates, plus two code-signing intermediates. The Chrome team reported that no TLS certificate chaining to the six website-issuing intermediates had been logged to Certificate Transparency before the block.

Here is the sequence in order:

- October 17: The report reaches Mozilla and Google. Chrome and Firefox block the certificates.
- October 19: Apple blocks the certificates.
- October 20: Microsoft blocks the certificates, and Mozilla publishes its [protection notice for Firefox users](https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/).
- October 22: eMudhra announces it will exit the global SSL/TLS certificate business.
- October 27: Chrome stops trusting emSign ECC Root CA – G3, with the change expected on the morning of October 27, Pacific time.

Software makers have shipped their own fixes too. Go released CVE-2026-111943, which rejects certificate chains containing the eight intermediates, in versions 1.26.10 and 1.27.3. Node.js 22.23.4, 24.22.1 and 26.12.1 updated their bundled certificate authority lists. Mozilla shipped Firefox 158.0.1, along with ESR 115.43.1, ESR 153.5.1 and NSS 3.131.1.

## Why weak keys turn into a trust problem

A certificate authority earns browser trust by vouching for websites. An intermediate CA signs the certificates that websites present, so whoever holds its private key can mint a certificate for any domain that browsers accept. That makes the failure bigger than one bad certificate, because the attacker never needs to touch the victim's website.

The strength of the keys is the most disputed detail. Researchers said the keys could be guessed in at most 256 tries, and one key is the number 4. Other accounts describe the weakness at about 8 bits, and one says the weak values were under 256. These descriptions point the same way, but the sources do not agree on the exact scale, and eMudhra has not yet published its root-cause report.

The problem was flagged early. eMudhra's own [statement on the incident](https://emudhra.com/en/post/certificate-security-incident) acknowledges that a May 2025 certificate revocation list problem involved the same six TLS intermediates, and that it was missed.

Revocation is not a complete answer. Browsers push block lists and check revocation, but some clients never receive those lists and do not check revocation at all. Those programs need their own updates, which is why the exposure is wider than browser warnings suggest.

## Whether your browser is safe after the eMudhra certificate compromise

For most people, the answer is yes, once they update. Chrome, Firefox, Apple and Microsoft pushed revocation lists that cover most browser users. Keeping browsers, phones and operating systems current is the main step for consumers, and they generally need nothing more.

The exposure sits elsewhere. Software that keeps its own trust store and skips revocation checks is the weak point, including servers, CI pipelines, Docker images and command-line tools such as curl and git. Build systems deserve extra attention. USA 24 recently reported how a [Gheist campaign used stolen GitHub tokens to dump repository secrets](https://usa-24.com/github-gheist-campaign-stolen-tokens/), a reminder that automated pipelines hold valuable credentials.

So far, public reports show no attacks. CoinDesk reported that no attacks had been reported as of its review. eMudhra says there is no evidence of misuse, but the keys could have been recovered at any point since April 2025, so silence is not proof. USA 24 has also covered how a [BeyondTrust zero-day was exploited for seven weeks by China-linked hackers](https://usa-24.com/beyondtrust-zero-day-cve-2026-102764/), which shows how long a quiet weakness can run before anyone sees it.

## What website operators must do before Chrome's October 27 removal

Google's guidance is direct. According to [The Hacker News](https://thehackernews.com/2026/10/emudhra-to-exit-global-ssltls-business.html), Google told website operators they “must immediately acquire and install a new TLS certificate from another PKI hierarchy included in the Chrome Root Store.” Use the time before the removal to work through a short checklist:

1. Find every certificate that chains to an eMudhra root, especially emSign ECC Root CA – G3, using a certificate viewer or openssl on each host.
2. Request a replacement from another certificate hierarchy in the Chrome Root Store. eMudhra says it will replace affected customers' certificates free through partners.
3. Plan for the G1 RSA roots separately. eMudhra says they will keep serving customers during the transition, but the timeline for that transition is unresolved.
4. Update CA bundles on servers and build agents, and rebuild container images so they pick up the change.
5. Update Go to 1.26.10 or 1.27.3, and Node.js to 22.23.4, 24.22.1 or 26.12.1.

Replacement is the step that cannot wait. A site that does nothing will fail for Chrome visitors after the removal, while a site that swaps early keeps service running. Treat the swap as a planned change with a rollback path, not an emergency patch.

## What eMudhra's exit means and what remains open

eMudhra's board decided to withdraw from the global SSL/TLS certificate business, according to its [October 22 press release](https://emudhra.com/en/press-release/emudhra-to-exit-global-ssl-tls-certificate-business). The company says SSL/TLS accounts for about 1% of its revenue, a figure that puts the exit in perspective. Yet its website says it has issued more than 60 million digital certificates overall. Chairman V. Srinivasan said in the release that social media scrutiny is “out of proportion” to the SSL/TLS business's place in the company.

US exposure is real but narrow in the sources. eMudhra Inc, the company's US entity, holds the G3C intermediates, and eMudhra says one US customer ecosystem is affected. The Internet2/InCommon higher-education trust federation runs on a platform eMudhra supplies, though the exit announcement does not explicitly name InCommon. Universities and research institutions that depend on that federation should ask their certificate teams for a direct answer.

Several questions remain open. Sources describe weak key generation rather than theft, but none names an attacker or confirms a theft investigation. Cloudflare says it became aware on October 19 at about 17:00 UTC, while Mozilla's record shows the report on October 17, so the timeline is not settled. eMudhra says the affected intermediates were not used to issue publicly trusted end-entity certificates, although some resulting certificates were submitted to Sectigo for cross-signing.

Chrome found no rogue certificates in Certificate Transparency logs, but logs cannot reveal misuse of certificates that were never logged. Whether Chrome will keep eMudhra's remaining CA certificates in its root store is also unresolved, as is the shape of the free replacement program and which partners will issue the certificates.

The next signal is Chrome's October 27 removal, which will show how many sites were still chaining to emSign when trust ended. eMudhra's promised root-cause report will decide whether this was a single failed key ceremony or a process gap that other certificate authorities need to audit in their own key handling.

## Frequently asked questions

### Is my browser safe after the eMudhra certificate compromise?

Most browser users are covered once Chrome, Firefox, Apple and Microsoft push their block lists, so keeping browsers, phones and operating systems updated is the main step. The bigger risk sits in servers, CI pipelines, Docker images and command-line tools that keep their own trust stores and skip revocation checks. Those need updated CA bundles and rebuilt container images.

### Which eMudhra certificate does Chrome stop trusting on October 27?

Chrome will stop trusting emSign ECC Root CA – G3, with the change expected on the morning of October 27, Pacific time. Website operators whose certificates chain to that root must replace them before then, following Google's guidance. eMudhra says its G1 RSA roots will keep serving customers during the transition, though that timeline is unresolved.

### Is eMudhra leaving the SSL/TLS certificate business?

Yes. eMudhra's board decided on October 22 to withdraw from the global SSL/TLS certificate business, and the company says it will replace affected customers' certificates free through partners. eMudhra says SSL/TLS is about 1% of its revenue. Its revocation services will continue until every certificate expires or is replaced.

### Were the eMudhra keys stolen or simply weak?

Sources describe weak key generation rather than theft. eMudhra said a flaw in an April 2025 key ceremony produced a second, weak set of keys that was published to root stores. No source names an attacker or confirms a theft investigation.

## Sources

1. [Protecting Firefox users following the compromise of eMudhra intermediate certificates](https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/)
2. [Eight eMudhra CA Keys Compromised, Triggering Emergency Fixes Across Browsers and Software](https://thehackernews.com/2026/10/eight-emudhra-ca-keys-compromised.html)
3. [Mozilla, Google, Apple block compromised eMudhra CA certificates](https://www.bleepingcomputer.com/news/security/mozilla-google-apple-block-compromised-emudhra-ca-certificates/)
4. [8 eMudhra certificates are compromised. Here's what you need to know](https://blog.cloudflare.com/emudhra-certificate-compromise/)
5. [eMudhra to Exit global SSL/TLS Certificate Business](https://emudhra.com/en/press-release/emudhra-to-exit-global-ssl-tls-certificate-business)
6. [eMudhra to Exit Global SSL/TLS Business After 8 Intermediate CA Keys Found Easily Guessable](https://thehackernews.com/2026/10/emudhra-to-exit-global-ssltls-business.html)
7. [2083449 - eMudhra: Private key compromise of Intermediate Certificates](https://bugzilla.mozilla.org/show_bug.cgi?id=2083449)
8. [Internet panics after 8 eMudhra private keys get cracked](https://www.coindesk.com/tech/2026/10/21/a-company-that-vouches-for-websites-had-secret-keys-so-weak-that-8-of-them-were-cracked)
9. [eMudhra Statement on Recent Certificate Security Incident](https://emudhra.com/en/post/certificate-security-incident)
10. [eMudhra CA compromise: eight private keys, and one of them is 4](https://www.aikido.dev/blog/emudhra-ca-compromise)
11. [eMudhra intermediate CA keys compromised; Go, Mozilla, Chrome, Apple and Microsoft distrust eight certificates](https://daily.dev/posts/emudhra-intermediate-ca-keys-compromised-go-mozilla-chrome-apple-and-microsoft-distrust-eight-ce-a03ptohlj)
12. [The eMudhra CA Compromise: How to Audit and Patch Linux](https://www.fosslinux.com/163042/emudhra-ca-compromise-linux-audit-patch.htm)