eMudhra breach: India's DSC chain is separate from the 8 blocked certificates

By Prakhar Shahi

Published · Updated

Flow chart: India's IT Act DSC chain from CCA root to user, beside the browser chain where 8 eMudhra keys were weak

Weak private keys in 8 eMudhra intermediate certificates led Google and Mozilla to block them, but MeitY says Indian DSC and eSign services are unaffected. How the IT Act's chain of trust works, from the CCA's root to a user's signature, and what comes next.

Original report · Explained

Does the eMudhra breach affect Indian digital signature certificates (DSCs)? No, according to the Ministry of Electronics and Information Technology (MeitY), which said on 21 October 2026 that DSC and eSign services are unaffected and that the impact on Indian websites was "very limited and for a very short interval" (The New Indian Express, 2026a). The flaw sits in eMudhra's separate global business: the private keys of 8 intermediate certificate authority (CA) certificates, 6 for TLS (website) certificates and 2 for code signing, were generated with too little randomness, CERT-In's advisory said (The New Indian Express, 2026b).

Keys made that way could be recovered almost instantly, Inc42 reported (Inc42, 2026). eMudhra says only 1 of the 8 was in production and none issued certificates to end users; Google found no certificates from the six TLS intermediates in public Certificate Transparency (CT) logs (The New Indian Express, 2026b; Inc42, 2026).

Mozilla and Google have blocked the six TLS intermediates, and Chrome will remove the emSign ECC Root CA - G3 from its root store from 27 October 2026 (The New Indian Express, 2026b). eMudhra shares fell 20%, hitting the lower circuit at Rs 431.55 on the BSE on 21 October (Inc42, 2026). See how every outlet covered the eMudhra breach.

These notes explain the two chains of trust involved, the IT Act sections behind India's chain, and what a compromised certifying authority means for users.

What it is

A digital signature can be trusted only because a chain of authorities vouches for the key behind it.

eMudhra runs two separate chains. The first, its Indian DSC and eSign business, is licensed and regulated by the CCA. The second, its global TLS and code-signing business, is trusted by browsers and audited under WebTrust by BDO International; MeitY is not involved in that audit (The New Indian Express, 2026a). The incident concerns only the second chain (The New Indian Express, 2026b).

Background and timeline

India's chain is 26 years old, and this is not the first time browsers have acted on an Indian certificate problem.

What the law says

India's chain of trust is set by the IT Act 2000, from the Controller at the top to the signature on a record.

The browser chain where the weak keys were found is overseen differently: browsers decide whether to trust it, it is audited under WebTrust, and MeitY is not involved in that audit (The New Indian Express, 2026a).

Institutions and the response

Indian regulators and the global browser makers have each acted on their own chain.

The numbers

The affected business is small for eMudhra, but the market reaction was not.

Arguments for and against

The government and the company say the impact is limited; Inc42 asks who watches an Indian CA that also works in global markets.

What happens next

The next date is 27 October, when Chrome starts removing the emSign root.

Questions people are asking

Is my Indian digital signature (DSC) affected by the eMudhra breach?

MeitY and eMudhra say DSC and eSign services under the CCA are unaffected (The New Indian Express, 2026a).

What is an intermediate CA certificate?

A certificate below a root certificate that can itself issue certificates; 8 of eMudhra's had weak private keys (Inc42, 2026).

Was customer data stolen in the eMudhra breach?

eMudhra ruled out a data breach, The Hindu BusinessLine reported; the problem is weak keys, and eMudhra says none of the 8 issued end-user certificates (The Hindu BusinessLine, 2026; Inc42, 2026).

What should organisations do?

Install the latest browser, app and system updates, and make sure revocation and distrust data reach their systems, CERT-In says (The New Indian Express, 2026b).

For students

GS paper: GS Paper III (cyber security; science and technology).

Key terms

Prelims facts

Previous-year questions

Mains practice question (250 words)

India's digital signature system rests on a chain of trust created by the IT Act 2000. Explain how this chain works, and, with reference to the eMudhra incident of October 2026, discuss the challenges of overseeing licensed certifying authorities that also operate in global markets.

Prelims practice question

Under the Information Technology Act 2000, who appoints the Controller of Certifying Authorities? (a) CERT-In (b) The Central Government (c) The Reserve Bank of India (d) The Supreme Court

Answer: (b), under section 17.

How we did this

We read the IT Act 2000 as published by PRS Legislative Research, sections 3 to 38, and the CCA's own account of its role, and built the trust-chain flow chart from them. We set the law against statements by eMudhra, CERT-In and MeitY on 21 October 2026, as reported by The Hindu BusinessLine, The New Indian Express and Deccan Herald, and against Inc42's analysis. We did not read CERT-In's advisory or the browser makers' notices directly. The previous-year questions come from CollectorBabu and Superkalam.

References

This story was produced, reviewed, edited and verified by the reporter before publication, with AI assistance where required.

Covered by 31 outlets across the spectrum: 23% left, 58% center, 16% right.

Who is covering this story

Sources

What an outlet bias classification means

More original reports

Related stories