CERT-In eMudhra Certificate Compromise Advisory: What Website Owners Should Do Before Chrome Removal on October 27

Image: Unsplash (free Unsplash licence) — Illustrative image: a digital padlock, representing the website certificates this advisory is about

TL;DR — The cert-in emudhra certificate compromise advisory what website owners should do story in one line: CERT-In advisory CIAD-2026-0050 (21 October 2026) confirms eight eMudhra intermediate CA keys were generated so weakly they can be recovered almost instantly — no misuse is confirmed yet, but any site chaining to the emSign ECC Root CA – G3 must replace its certificate before Chrome removes that root on 27 October.

📌 KEY HIGHLIGHTS

• What broke: private keys for eight eMudhra intermediate CAs — six for TLS website certificates, two for code signing — were generated with insufficient randomness. The P-384 keys had values smaller than 256, so anyone can recompute them from the public certificates; one recovered key is literally the number 4.
• What did NOT happen: eMudhra says its systems were not hacked, no customer data was breached, its root CA keys are safe, none of the eight intermediates ever issued an end-entity certificate, and only one was ever deployed in production. CERT-In says there is no confirmed malicious use as of 21 October.
• Browsers moved fast: a researcher reported the flaw on 17 October; Chrome blocked the keys the same evening, Android followed on 19 October, and Apple and Microsoft blocked them by 20 October.
• The hard deadline: Chrome will remove the emSign ECC Root CA – G3 from its root store in a release reaching all devices on Tuesday 27 October 2026. Legitimate sites still chaining to that root will break until they migrate.
• Not affected: India's regulated Digital Signature Certificate (DSC) and eSign services run on separate infrastructure under the Controller of Certifying Authorities — MeitY and eMudhra both say they are completely unaffected.

What happened?

Every padlock in your browser rests on a chain of trust: a root authority vouches for an intermediate authority, which signs the certificate a website shows you. On 21 October 2026, India's CERT-In published advisory CIAD-2026-0050 after eMudhra Limited — an Indian certification authority whose certificates are sold globally under the emSign brand — reported that the private keys behind eight of its intermediate certificates were compromised. Not stolen, exactly: worse in one way, because they never needed stealing. According to eMudhra's stock-exchange filing, a flaw in its key generation ceremony on 30 April 2025 produced a second, weak set of keys alongside the strong ones, and the weak set is what reached the browser root stores. A researcher who signs himself "Wayne" spotted that the keys could be reverse-engineered — reportedly with AI assistance — and alerted Apple, Google, Microsoft and Mozilla on 17 October. Security researcher Scott Helme later recovered all eight private keys on a laptop in under a second.

Why does that matter? Whoever holds an intermediate key can, in theory, mint a trusted certificate for any website — a bank, a payment page, a government portal — and use it to impersonate that site or sit in the middle of encrypted traffic. The two compromised code-signing keys could similarly make malicious software look legitimately signed. That is the risk CERT-In is warning about. It is a potential, not a confirmed attack: Chrome's team notes that no certificate chaining to the six TLS intermediates had been logged to Certificate Transparency before the block landed, and CERT-In states plainly that public disclosures do not establish confirmed malicious use so far.

Cert-in eMudhra certificate compromise advisory what website owners should do — the deadline table

Date	What happened / what happens	Who must act
17 Oct 2026	Researcher reports weak keys; Chrome blocks the six TLS intermediates via CRLSet within hours; Mozilla blocks via OneCRL the same night	— (automatic for browser users)
19–20 Oct 2026	Android block via Google Play System Updates; Apple and Microsoft block; Go, Firefox, Node.js and Linux trust stores ship fixes	Developers: update runtimes and trust bundles
21 Oct 2026	CERT-In advisory CIAD-2026-0050 published; MeitY forms a special investigation team; eMudhra files its BSE disclosure	Website owners: start the checklist below
22 Oct 2026	eMudhra board votes to exit the global SSL/TLS business — free partner-CA replacements for affected customers; G1 RSA root serves until transition done; revocation/status services stay live until every issued cert expires or is replaced; ~30,800 unexpired certs chained to G3 (Chrome CT count); shares down ~40% in two days	Customers: take the free replacement; the 27 Oct Chrome removal still stands
27 Oct 2026	Chrome removed emSign ECC Root CA – G3 from the Chrome Root Store (deadline Tuesday morning PDT / Tuesday evening IST, 27 October)	Any site still chaining to G3 breaks in Chrome until it migrates

UPDATE — 22 October 2026: eMudhra's board has decided to voluntarily wind down its global SSL/TLS certificate business entirely. The company will contact affected customers and arrange free replacement certificates through partner CAs, keep its G1 RSA root certificates serving until the transition is complete, and keep revocation and status services running until every certificate it issued has expired or been replaced. Its India-regulated DSC/eSign businesses and the CertiNext platform continue. The TLS line was about 1% of eMudhra's revenue, and its shares fell roughly 40% in the two days after the disclosure. The 27 October Chrome removal of the emSign ECC Root CA – G3 still stands — if your site chains to G3, migrate now.

UPDATE — 28 October 2026: The Chrome removal deadline for the emSign ECC Root CA – G3 has now passed — it was due Tuesday morning Pacific time on 27 October (Tuesday evening in India). As of the last checked status (Convika's tracker, last updated 27 October, status as of 15:50 JST 27 October), Google's post had no confirmation update, but Chromium's source root store v43 no longer lists the root. So: sites still chaining to G3 will break in Chrome for visitors as the rollout reaches them — treat the removal as in effect for planning, not as a confirmed landing announcement. One gap beyond browsers: software with its own trust store (servers, containers, build pipelines) does not get the browser fix automatically — an independent 24 October scan of 30 common Docker images found 10 still shipping the G3 root, so rebuild images with fresh base layers rather than assuming an updated browser means an updated backend.

The action list is short, and it is mostly for website operators, not everyday users. First, check whether your site's certificate chains to emSign ECC Root CA – G3 or to any of the eight named intermediates (the EM DV, OV and EV TLS CA – G3B and G3C certificates, plus the two OV code-signing CAs). If it does, replace it now with a certificate from a hierarchy browsers still trust — eMudhra says it is issuing replacements and moving affected customers to another root. Second, update everything that verifies certificates: browsers, operating systems, Node.js, Go, Python's certifi bundle and Linux ca-certificates packages have all shipped fixes, because apps that never check revocation lists keep trusting the bad keys until their trust store changes. Third, confirm your applications reject chains passing through the compromised keys, and keep an eye on Certificate Transparency logs for your domains. And for everyone, the oldest rule in this business applies with fresh force: never click through a browser certificate warning.

Image: Unsplash (free Unsplash licence) — Illustrative image: cybersecurity monitoring

Why it matters for India readers

This is a global trust incident with an Indian company at the centre, and the distinction MeitY drew on 21 October is the one most readers need: eMudhra runs two separate businesses. The one in trouble is its international TLS business — about 1% of company revenue, by its own filing — which sells the website certificates browsers trust. The other is the India-regulated business of Digital Signature Certificates and eSign, supervised by the Controller of Certifying Authorities on separate infrastructure, and both the ministry and the company say it is untouched. So the DSC you use to sign tax filings or company documents is not affected, and MeitY described the impact on Indian websites and apps as "very limited and for a very short period", while still forming a special team to investigate and pushing back on social-media fear-mongering. The market, for its part, was less calm: eMudhra shares fell about 20% in Mumbai on 21 October. For a reminder of what a confirmed India data incident looks like by contrast, see our SBI customer data leak explainer and what customers should do now, and developers should also apply the runtime fixes covered in our Node.js October 2026 security release update guide, which already rejects chains containing these eight keys.

Should you care?

✅ Care now if you run a website, an app backend or any server using emSign certificates — ⏳ ordinary users mainly need one update. If your certificate chains to the G3 root, 27 October is a hard deadline, not a suggestion: after Chrome's removal, visitors will hit warnings or failed connections until you migrate. If you build software, rebuild and update — Go, Node.js, Python and Linux fixes only protect you once installed. If you simply browse, keep Chrome, Firefox and your phone updated (the blocks were pushed automatically) and treat any certificate warning this week as a stop sign. Do not panic about DSC or eSign: on the evidence published so far, they are a different system entirely.

FAQs

What did CERT-In say about the eMudhra certificate compromise?
In advisory CIAD-2026-0050 on 21 October 2026, CERT-In said private keys for eight eMudhra intermediate CA certificates — six TLS and two code-signing — were compromised because they were generated with insufficient cryptographic randomness, making them recoverable almost instantly. It warned the keys could be used to issue fraudulent TLS certificates, impersonate websites and intercept or modify encrypted communications, while noting that no confirmed malicious use had been established as of the advisory date.

Are eMudhra digital signature and eSign services affected?
No, according to both eMudhra and MeitY. India's Digital Signature Certificate and eSign services are regulated by the Controller of Certifying Authorities and run on separate infrastructure from the global TLS business where the weak keys were created. The ministry said those services remain completely unaffected and continue to operate normally.

What should website owners using emSign certificates do before October 27?
Check whether your certificate chains to emSign ECC Root CA – G3 or to any of the eight compromised intermediates, and if so replace it with a certificate from a trusted hierarchy before Chrome removes the G3 root on 27 October 2026 — eMudhra is issuing replacements to affected customers. Also update your servers' trust stores, confirm your applications reject chains through the compromised keys, and monitor Certificate Transparency logs for your domains.

Can the compromised eMudhra keys be used to impersonate websites?
In theory, yes — that is exactly the risk CERT-In flagged. An intermediate CA key can sign a certificate for any domain, so a holder could impersonate a legitimate website or intercept encrypted traffic in a man-in-the-middle attack. In practice, Chrome found no certificate chaining to the six TLS intermediates in Certificate Transparency logs before it blocked the keys within hours of the 17 October report, and no malicious use has been confirmed so far.

TAKEAWAY
The keys were not stolen — they were born weak, and browsers have already slammed the door. What remains is a migration deadline: if your site trusts the G3 chain, replace the certificate before 27 October.
Follow India Tech on TechByCountry for the next hourly update.

Sources: Livemint — eMudhra intermediate CA certificates compromised, explained (CERT-In advisory CIAD-2026-0050, 21 Oct 2026) • The Hacker News — Eight eMudhra CA Keys Compromised, Triggering Emergency Fixes Across Browsers and Software (21 Oct 2026) • Indian Express — eMudhra security certificate flaw: what Chrome and Firefox users must know (21 Oct 2026) • Reuters — Indian firm eMudhra exits global digital certificates business after vulnerability disclosure (22 Oct 2026) • The Hacker News — eMudhra to Exit Global SSL/TLS Business After 8 Intermediate CA Keys Found Easily Guessable (22 Oct 2026). Updated 28 Oct 2026.