eMudhra Certificate Authority Keys 'Hacked': 8 Certificates Blocked By Chrome, Firefox, Apple And Microsoft- All Details Explained
Private keys for eight intermediate certificates run by Indian certificate authority eMudhra have been compromised. Browsers, operating systems and software makers have moved to block them. eMudhra has revoked all eight.
Ni News18 Tech··27K nabasa
eMudhra Certificate Authority Keys 'Hacked': 8 Certificates Blocked By Chrome, Firefox, Apple And Microsoft- All Details Explained
Private keys for eight intermediate certificates run by Indian certificate authority eMudhra have been compromised. Browsers, operating systems and software makers have moved to block them. eMudhra has revoked all eight.
The report reached Mozilla on Saturday, 17 October 2026, at 20:06 UTC. It came from a researcher named Wayne. Mozilla and Google’s Chrome Root Program confirmed the compromise on 20 October.
The certificates could have let an attacker forge HTTPS certificates for any website. The block came within hours in Chrome and Firefox. No forged certificate has been found so far. Many other tools need a manual update to be safe.
What Happened?
Question
Answer
Who is affected
eMudhra, an Indian certificate authority that sells under the emSign brand
What was compromised
Private keys of eight intermediate CA certificates
Split
Six for TLS (HTTPS) and two for code signing
When reported
17 October 2026, 20:06 UTC
Revoked by eMudhra
18 October 2026 (reason: CA compromise)
Forged certificates found
None so far in Chrome’s Certificate Transparency (CT) log search
How the keys leaked
Not yet known
Official eMudhra statement
Published 20 October 2026; investigation ongoing
What is a Certificate Authority, and why does this matter
Every secure website you visit shows a padlock. That padlock depends on a digital certificate. A certificate authority (CA) issues it. The CA vouches that the site is who it says it is.
The system works like a chain. A root CA sits at the top. Browsers and operating systems trust it by default. The root signs certificates for intermediate CAs. The intermediates then issue certificates to websites.
Each intermediate has a private key. That key is the secret that lets it sign certificates. If someone else gets the key, they can sign certificates too. Browsers would treat those certificates as valid until the key is blocked.
That is why intermediate keys are so sensitive. They sit high in the chain. A holder can create certificates for any domain without the checks a real CA must do.
Mozilla received a report on 17 October at 20:06 UTC. The report was forwarded by the Chrome Root Program. It said the private keys of eight eMudhra intermediates had been compromised.
To prove it, the researcher signed a short message with each of the eight keys. Anyone can check those signatures with standard tools such as OpenSSL. The keys themselves were not published.
eMudhra acknowledged the report at 21:29 UTC the same day. It said it was investigating and had told Sectigo. Sectigo had cross-signed some of the affected certificates.
Timeline
Date (UTC)
Event
17 Oct, 20:06
Mozilla receives the report
17 Oct, 21:29
eMudhra acknowledges the report and says it is investigating
17 Oct
Firefox and Chrome block the eight certificates
17 Oct, by 22:59
Mozilla’s OneCRL update reaches all Firefox users with standard settings
18 Oct
eMudhra revokes the eight certificates
19 Oct
Sectigo revokes its cross-signed copies. Apple blocks the certificates. Other trust stores are notified. Cloudflare learns of the issue at about 17:00
20 Oct
Microsoft blocks the certificates. Mozilla ships Firefox updates and removes a root from its trust list. eMudhra publishes its statement
Sources differ on one date. Some reports put the Go release on 19 October. The Hacker News report says 20 October.
8 affected certificates
Certificate
Type
Operated by
EM DV TLS CA – G3B
TLS, domain validated
eMudhra BV (Netherlands)
EM OV TLS CA – G3B
TLS, organisation validated
eMudhra BV (Netherlands)
EM EV TLS CA – G3B
TLS, extended validation
eMudhra BV (Netherlands)
EM DV TLS CA – G3C
TLS, domain validated
eMudhra Inc (United States)
EM OV TLS CA – G3C
TLS, organisation validated
eMudhra Inc (United States)
EM EV TLS CA – G3C
TLS, extended validation
eMudhra Inc (United States)
EM OV CS CA – G3B
Code signing
eMudhra BV (Netherlands)
EM OV CS CA – G3C
Code signing
eMudhra Inc (United States)
All eight were valid from 30 April 2025. The six TLS certificates chain to emSign Root TLS CA – G3. According to Chrome’s root programme, they chain on to emSign ECC Root CA – G3. That root is in the Chrome and Apple stores. It was also in Mozilla’s store until 20 October. The two code-signing certificates sit under emSign Root CS CA – G3.
They are trusted under the Mozilla, Microsoft, Apple and Chrome root programs. Many other trust stores copy from these programs.
How the keys were exposed
Nobody has said how the keys left eMudhra, or when. It is also not known whether anyone besides the researcher has them. Some reports point to weak keys instead of theft. Cloudflare says the keys themselves are weak. It says an attacker can therefore create a forged certificate for any domain.
The Register quotes security researcher Helme. He said he recovered the keys from the public certificates on his laptop in under a second. The report’s headline says one of the keys was the number 4. The Register describes the keys as far too easy to guess.
Online commenters have gone further. Some claim all eight keys are a single byte. That claim comes from a forum thread. It has not been confirmed by eMudhra, Mozilla or Chrome. Treat it as unverified.
Some commenters also blame a mistake in the key generation ceremony. eMudhra says the intermediates were created in a ceremony in April 2025. eMudhra has not said what went wrong. The cause is still unconfirmed.
Heise reports that the keys were stolen. That wording sits poorly with the weak-key reports. Until eMudhra publishes a root-cause analysis, the exact method stays unknown.
The Risks
An attacker with one of these keys could sign a certificate for any website. Examples would be a bank, an email service or a government portal. Mozilla says such a certificate could let an attacker impersonate a site. The attacker could also read or change traffic.
However, there is a catch. The attacker must sit between you and the site. This is called a man-in-the-middle attack. It can happen on public Wi-Fi, on a hijacked network or through a compromised router. It is not something anyone can do from far away with no access to your connection.
The two code-signing certificates carry a different risk. Code-signing certificates tell your system that software comes from a trusted publisher. A forged one could make malware look legitimate. The sources focus mostly on the TLS risk. The code-signing angle follows from what these certificates are for.
Who is most at risk
Clients that do not check revocation. Many tools never fetch revocation data. They need a software update.
Linux systems. Go’s cryptography maintainer says Linux root stores are too poorly maintained for revocation to reach applications.
Software that bundles its own list of trusted certificates and has not updated.
Users on networks they do not control.
Who is already protected
Firefox and Chrome users. Both were covered through OneCRL and CRLSets.
Apple devices, which have blocked the certificates since 19 October.
Microsoft’s trust store, updated on 20 October.
Clients that always fetch fresh revocation data and refuse to connect when it is missing. Mozilla says they need no further steps.
eMudhra Publishes Statement:
The incident involves a specific set of intermediate CA certificates from a key generation ceremony in April 2025.
Its root CA private keys are not affected. Its other intermediate CAs are not affected.
None of the affected intermediates issued any end-entity certificates. This includes the one used in production.
It started incident response, contained the certificates and is working with browser and root-store operators.
Mozilla also said no public TLS server certificates were issued under the affected roots. The exception was internal test certificates. A third-party outlet relayed that statement. Cyber Kendra and The Hacker News both noted that eMudhra’s own trust-services page had no notice about the incident as of 20 October. The statement went up later that day.
The Register reported that eMudhra had not answered its questions. It described the 60-million-plus certificates eMudhra says it has issued as untrustworthy. That goes further than eMudhra’s own statement. eMudhra says the incident is limited to the eight intermediates and none of them issued end-entity certificates. On that account, existing customer certificates are not directly affected.
What is eMudhra
eMudhra is a public key infrastructure company headquartered in Bangalore. It is a certifying authority licensed by the Government of India. Its website says it has issued over 60 million digital certificates. It also says it has partnered with 500 organisations in 21 countries. It also claims it serves 10 out of 10 of India’s top banks.
It sells through companies in India, the United States and the Netherlands. It has roots in the Mozilla, Chrome and Apple root stores.
How the industry responded
Vendor or project
Action
Mozilla Firefox
Blocked via OneCRL. Firefox 158.0.1 and ESR 115.43.1 and 153.5.1 ship the block for users whose settings stopped the OneCRL update. Mozilla also removed the root that signed the affected intermediates in NSS 3.131.1
Google Chrome
Blocked via CRLSet. Chrome Root Store version 43 will drop the upstream eMudhra root. Chrome is also reviewing the status of eMudhra’s remaining CA certificate
Apple
Blocked on 19 October
Microsoft
Blocked on 20 October
Go
Go 1.27.3 and 1.26.10 reject any chain that contains one of the eight keys (CVE-2026-111943). Programs must be rebuilt
Cloudflare
Patched services and released updates for the WARP app, the Cloudflare One client and cloudflared. The Cloudflare One Agent on iOS was still waiting for app review at the time of its post
Python certifi
Fix released (2026.10.19)
Rust webpki-roots
Fix released (1.0.10)
Node.js
Patch pending
Composer ca-bundle
Patch pending
Debian ca-certificates
Pending
Go chose to hard-code the eight keys into its standard library. This is a key-level block. It also catches the Sectigo cross-signed copies, which share the same keys. Blocking only the eMudhra root would not be enough. An attacker could still present a chain through the Sectigo root.
Go’s cryptography maintainer said putting the keys in code was the only option for now. His reason was that revocation does not reliably reach applications on Linux.
How to secure your devices and systems
If you are a regular user
Update your browser. For Firefox, install 158.0.1 or the matching ESR release. Chrome users are covered by its CRLSet update.
Keep your phone and computer operating system up to date. Apple and Microsoft have already pushed blocks.
Update apps that connect to the internet, such as VPN clients and developer tools.
Be careful on public Wi-Fi until your software is updated. The attack needs the attacker to sit on your connection.
Test your browser at emudhra.we-have-a-problem.com. The site tries a connection for each affected certificate. It shows whether your browser still trusts them.
If you run servers or build software
Update Go to 1.27.3 or 1.26.10. Then rebuild your programs. Updating alone is not enough.
Update Python’s certifi to 2026.10.19 or later. Update Rust’s webpki-roots to 1.0.10 or later.
Watch for Node.js and Composer ca-bundle patches. Both are pending.
Update your Linux ca-certificates package. Ubuntu, Arch Linux, Gentoo and Chainguard have shipped updated packages. Debian is still pending.
If your distribution has no update yet, expert users can distrust the affected roots by hand in the system trust store. The disclosure site lists the steps.
macOS blocks the certificates in the system. But the built-in curl reads a certificate file that has not been updated. It does not check revocation. Do not rely on it.
Homebrew’s ca-certificates package from 25 September 2026 (version 2026-09-25_1) already excludes the affected roots by public key.
If you manage security for an organisation
Audit your environment. Find any system that trusts certificates signed by eMudhra. Many teams may not know they depend on them.
Make clients fetch current revocation data. Set them to refuse a connection when that data is missing.
Where your trust store can block specific intermediates, ship that block now. Do not wait for the next vendor release.
Check any system that pins or bundles its own certificate list.
Update Cloudflare client apps if you use WARP, Cloudflare One or cloudflared.
If you buy certificates from eMudhra, ask the company directly about your certificates. Its statement says none of the affected intermediates issued end-entity certificates.