← sources

Everything about eMudhra compromise and what you should do

source: reddit (reddit:IndiaTech)published 2026-10-21 05:28ingested 2026-10-22 02:39

retained text



# What actually happened

In April 2025, eMudhra, Indian Certificate Authorrity generated 8 intermediate certificates with very weak private keys. One of them was a single digit "4" lol. Others were like 56, 115, etc

Anyone could recover these keys in under a second and create fake HTTPS certificates for any website that browsers would trust.

One researcher reported this on 17 October 2026. Google, Mozilla, Apple, Microsoft has blocked the bad certificates within hours. This came to limelight to everyone today morning.

eMudhra is licensed by India’s CCA/MeitY and works on government projects too.

# What you should do..

* Update your browser and operating system right now (Chrome, Firefox, Edge, Safari, Windows, Android, iOS, etc as applicable)
* On Linux, update your `ca-certificates` package
* Check if your browser is still vulnerable: open this page and scroll down: [https://emudhra.we-have-a-problem.com/](https://emudhra.we-have-a-problem.com/)
* If you run a website that uses an eMudhra/emSign certificate, get a new certificate from another CA as soon as possible

Most regular users are already protected once their browser is updated.

# Simple explanation for non-tech people

(credit: u/just_sm_so_relax;; [original comment](https://www.reddit.com/r/IndiaTech/comments/1xb0bmh/comment/19rf0bsn18nj4/))

>Suppose your bank is SBI. You use Chrome to go to their website [sbi.in](http://sbi.in) for internet banking.

>But your neighbour could have hacked your wifi router and redirected all your internet through his computer. So what you think is [sbi.in](http://sbi.in) is actually a website your neighbour is operating.

>Browsers (like Chrome) protect against this by using https.

>This is how https works:

>SBI IT team goes to a certifying authority (CA), shows them documentation to prove that they are the "real" SBI.

>There are many CAs around the world. eMudhra in India is one of them.

>CA examines the documentation, and once they are satisfied, they issue a digital certificate ("cert") to SBI which essentially says "we, eMudhra, hereby certify that the holder of this certificate is the real SBI".

>All the major browsers (Chrome, Firefox, Brave, etc.) are programmed to trust some CAs - I think there are some 100 or 150 CAs whom they trust. eMudhra is one of them. Basically the browsers have logic that says that "trust any site that is certified by any of these 150 parties"

>Now, Step 3 is important. Once eMudhra is satisfied that SBI is really SBI, they use a really long 116-digit number to generate the SBI cert. This makes forging the certificate impossible. Some other bad guy (like your neighbour) cannot generate a cert for his own website and make a certificate that says "we, eMudhra, hereby certify that the holder of this certificate is the real SBI".

>Except, the dumbasses at eMudhra didn't use a 116-digit number. They used a 1-digit number, the number "4".

>So now, it is easy for your neighbour to make his own cert for his own website, and make it say "we, eMudhra, hereby certify that the holder of this certificate is the real SBI".

>What is the remedy?

>Browsers will now have to be reprogrammed to say "stop trusting certificates that are signed by eMudhra". Every laptop, PC, server, mobile phone, IoT device on the planet will have to be reprogrammed.

document fetched 2026-10-22 00:28 · canonical https://reddit.com/r/IndiaTech/comments/1xbeni7/everything_about_emudhra_compromise_and_what_you