Security Advisory: eMudhra emSign CA Key Compromise
On October 17, 2026, researchers found that the private keys behind eight intermediate certificates from eMudhra (brand name "emSign"), one of India's licensed ..
On October 17, 2026, researchers found that the private keys behind eight intermediate certificates from eMudhra (brand name "emSign"), one of India's licensed Certifying Authorities, were critically weak. Six of these intermediates issue TLS certificates for HTTPS websites, the other two issue code-signing certificates that vouch for software.
A Certifying Authority's key is the thing every browser, mail client and government portal trusts without asking questions. When that key can be guessed, the trust it underwrites is gone. Mozilla, Google, Apple and Microsoft have already blocked the affected certificates, but the story is not over: Mozilla has pulled one eMudhra root entirely, and Google is still reviewing the rest.
Why this is serious
Anyone holding these keys could mint certificates that look completely legitimate. That breaks the three things certificates exist to guarantee: that you are talking to the right website, that software really came from its publisher, and that the systems you connect to are who they claim to be.
Forged websites that pass every browser check
An attacker with these keys could issue a valid-looking HTTPS certificate for any website — your bank, your email provider, a government portal. On an untrusted network such as public Wi-Fi or a compromised router, they could sit in the middle of your connection, read and alter traffic, and the padlock would still show. Devices that have not received the browser and OS blocks remain exposed.
Malware that carries a trusted publisher's signature
Two of the compromised intermediates issue code-signing certificates. With those keys, an attacker could sign malicious software so it appears to come from a legitimate publisher. Operating systems and security tools that rely on that signature would treat the malware as trusted, on any machine that hasn't received the fix.
India's digital signature backbone is in the blast radius
eMudhra is one of India's dominant Certifying Authorities for government-mandated Digital Signature Certificates (DSCs). These DSCs sign income tax e-filings, GST returns, MCA/ROC filings and e-tenders. As the fix rolls out, teams using DSC tokens may hit certificate trust warnings on these workflows and, in rare cases, service interruptions — right when filings are due.
Payments and supply chains, not just browsers
Where eMudhra certificates secure machine-to-machine links — mutual-TLS to payment gateways, UPI/NPCI rails, Account Aggregator APIs, vendor remote access or firmware updates — the impact is worse than a browser warning. A distrusted certificate there can stop transaction processing outright, and a forged one can turn a trusted supplier channel into an attack path.
Who is at risk: The risk is confined to certificates issued under the eMudhra/emSign root hierarchy — but if you use them, you need to act now.
How an attack could play out
The scenarios below show what an attacker could do with these keys, step by step. They are illustrations of the risk, not reports of attacks seen in the wild. In each one, the victim sees nothing unusual — that is what makes a CA key compromise so dangerous.
1. The Free-Wifi Login
An employee connects to free Wi-Fi at an airport or café. The attacker controls the hotspot.The employee opens their webmail or banking site. The attacker intercepts the connection and presents a forged certificate for that exact site.The device hasn't received the latest browser/OS update, so it trusts the forged certificate. The padlock shows. No warning appears.
Result: the attacker reads the password, session cookies and everything on the page, and can log in as the employee later.
2. The "verified" invoice viewer
An attacker builds malware disguised as an invoice viewer or a GST filing utility, and signs it with a code-signing certificate from a compromised eMudhra intermediate.They email it to the accounts team as an attachment from a "vendor".When opened, the operating system shows a verified publisher instead of an "unknown publisher" warning, so the employee clicks through.
Result: the attacker gets a foothold on the finance team's machine — access to banking sessions, DSC tokens and payment approvals.
3. The fake "DSC renewal" notice
Attackers use the news itself as bait: "Your eMudhra Digital Signature Certificate must be re-issued after the security incident."The link leads to a convincing portal — on an attacker-controlled network, it can even carry a valid certificate for the real domain.The employee enters their DSC token PIN, portal credentials, or installs a "DSC update utility".
Result:the attacker can sign GST, income tax or MCA filings as the company, or gains a foothold on the device through the installed malware.
4. The intercepted payment API
A fintech's servers talk to a payment gateway or Account Aggregator API over mutual TLS, trusting the eMudhra chain. An attacker with network access (a compromised router, cloud misconfiguration or rogue insider) impersonates the gateway using a forged certificate. The fintech's systems accept it and send live transaction or customer financial data.
Result: customer data leaks, transactions are altered or replayed — and when the real certificates are distrusted, legitimate transactions may stop entirely.
5. The poisoned software update
A factory's equipment or a vendor's remote-access tool checks for updates from a server secured by an eMudhra certificate. An attacker on the network path impersonates that update server with a forged certificate. The device downloads a tampered update — signed with a forged code-signing certificate, so even a signature check passes — or connects to an attacker-controlled "vendor" session.
Result: malware lands inside the plant network through a channel everyone considered trusted — a supply-chain compromise.
The common thread: every scenario abuses a check that normally means "this is safe" — the padlock, the verified publisher, the trusted vendor. That is why patching, certificate rotation and healthy suspicion of anything certificate-related matter so much right now.
Sequence of Events
The eight affected intermediates are six TLS issuers (EM DV, OV and EV TLS CA - G3B/G3C) and two code-signing issuers (EM OV CS CA - G3B/G3C). Mozilla found their private keys were tiny integers below 256, recoverable in under a second. eMudhra's preliminary explanation is a flawed key-ceremony script and "human errors in multiple steps of the process"; it is re-verifying every key ceremony it has performed (Bugzilla). That uncertainty is why we recommend rotating eMudhra-issued certificates even without direct evidence of compromise.
Who is most exposed
Any organization that uses eMudhra/emSign certificates for websites, email signing or DSCs is affected. Two sectors carry extra risk.
Banking and fintech
Transactions can break. Check mutual-TLS links to payment gateways, UPI/NPCI rails and Account Aggregator APIs for certificates chaining through eMudhra/emSign. This is higher severity than browser TLS: it can halt transaction processing, not just show a warning.
Audit evidence is at stake. Verify DSC signatures on RBI/SEBI filings and loan documentation against the compromised intermediates before relying on them for audit.
Regulators will ask. RBI's Cyber Security Framework (Annex 1) sets baseline requirements for certificate-based authentication and incident reporting. Document your eMudhra exposure now, not at the next audit.
Manufacturing
Compliance filings can stall. GST e-invoicing, e-way bills and DGFT/customs filings commonly use DSC signing. Confirm continuity with your ERP or compliance vendor if they rely on eMudhra.
Supply-chain trust is in question. If vendor remote access, firmware updates or partner portals use eMudhra-issued certificates (TLS or code-signing), treat this as a supply-chain trust issue, not just a browsing one.
What to do now
Patch every company device. Browsers and OS must be current: macOS Sequoia 15.8.1+ / Tahoe 26.7.1+, current Windows, current Linux ca-certificates. This is a rolling fix, not a one-time one, because an eMudhra root is still under review.
Inventory your certificates. Check whether any internal or vendor-facing TLS certificates were issued by eMudhra/emSign, and consider rotating them given the uncertainty around the CA's key-generation process.
Watch DSC-dependent workflows. If teams use eMudhra/emSign DSC tokens for income tax, GST or MCA portals, watch for certificate warnings and verify through official channels, never through links in email.
Treat "renewal" emails as phishing. Unexpected "certificate renewal" or "digital signature update required" emails, especially ones mentioning eMudhra, DSC or CCA, are phishing until independently verified.
Check your software supply chain. Ask vendors whether any software or updates you install are signed with eMudhra/emSign code-signing certificates, and update non-browser tools that keep their own trust stores (for example Go 1.27.3/1.26.10 and Python certifi 2026.10.19).
How Ravenmail is responding to this situation
Retroactive hunt for existing clients : scanning your mailbox data (via our existing mail API access) for S/MIME-signed messages whose signing certificate chains to the eight compromised intermediates or affected eMudhra roots.
Ongoing detection: a new rule flags any mail using those certificate fingerprints and checks outbound links for sites serving fraudulent certificates from this chain.
Phishing watch: monitoring for campaigns exploiting this incident, such as fake "certificate renewal" emails.
Direct notification: we'll tell you if the hunt finds anything in your environment, and confirm it even if we find nothing.
Sources and further reading
Primary sources
Mozilla Security Blog — Protecting Firefox users following the compromise of eMudhra intermediate certificates (Oct 20, 2026)
Mozilla Bugzilla — Bug 2083449: Private key compromise of eMudhra Intermediate Certificates (affected certificates and eMudhra's preliminary root-cause statement)
Mozilla dev-security-policy — Compromised eMudhra Intermediate Certificates
Reserve Bank of India — Cyber Security Framework in Banks (RBI/2015-16/418, June 2, 2016)
News coverage
The Register — Indian certification authority eMudhra's private keys compromised; one of them was the number 4
BleepingComputer — Mozilla, Google, Apple block compromised eMudhra CA certificates
The Hacker News — Eight eMudhra CA Keys Compromised, Triggering Emergency Fixes Across Browsers and Software
Sign-up for a trial
Go live in minutes
