blog

eMudhra: The Day a Certificate Authority's Secret Keys Turned Out to Be "4"

If you've never thought about certificate authorities, that's the point. They work quietly in the background until one of them has a very bad week. In October 2026, India's eMudhra had that week, and it's worth understanding what happened, because the lesson applies well beyond one company.

7 min readupdated by Syed Khaleel Ahmed#emudhra#certificate-authority#ca-compromise#cybersecurity#pki#tls#ssl#private-key

First, a quick primer

When you open a website and see the little padlock, your browser has checked that the site's certificate was issued by someone it trusts. That someone is a certificate authority (CA). Browser makers like Google, Mozilla, Apple and Microsoft keep lists of CAs they trust, and a CA earns its place by following strict rules.

CAs are organised like a family tree. A root certificate sits at the top, and underneath it are intermediate certificates that do the day-to-day work of issuing certificates to websites. Every certificate has a secret private key, and the whole system depends on that key being truly secret and truly random. If someone gets hold of an intermediate CA's private key, they can mint "valid" certificates for any website they like and impersonate it.

eMudhra is a Bengaluru-based, publicly listed company and one of India's largest licensed certifying authorities. It also ran a separate global business selling website (TLS) and code-signing certificates under the emSign brand.

What happened

On April 30, 2025, eMudhra held a key generation ceremony, the formal, scripted process where a CA creates its keys. Eight intermediate CA keys came out of it. Six were meant for website TLS certificates and two for code signing.

Those keys were catastrophically weak. Keys like these should be enormous numbers, around 116 digits long. These were all below 256. One was literally the number 4, and two others were 56 and 115. Security researcher Scott Helme said he recovered all eight in under a second, and Mozilla described the keys as essentially zeros apart from the last byte.

So nobody "hacked" eMudhra. There was no break-in and no stolen data. The keys were broken the moment they were created, and since certificates are public, anyone could work out the private key from the public certificate. According to analysis from the OpenVPN team, that left them exposed for roughly 18 months, from April 2025 until October 2026.

eMudhra's own explanation is that a flaw in the ceremony script produced a second, weak set of keys alongside the intended ones, and the weak set was mistakenly used because the labels looked similar. The company says these intermediates were created for exporting to US and European data centres, and that only one was ever deployed in production. It also says none of them issued any website certificates. Independent reconstructions haven't confirmed that account, so treat it as the company's version for now. The flaw slipped through two external audit cycles, and eMudhra's cofounder admitted he didn't know how.

How it was discovered

On October 17, 2026, at 20:06 UTC, a researcher known only as "Wayne" reported to Mozilla, via the Chrome Root Program, that the private keys of eight eMudhra intermediates had been compromised. According to reporting, he found the issue while running a check against CCADB, the shared database of CA certificates. To prove it, he signed a short message with each of the eight keys and sent the proof to Apple, Google, Microsoft, Mozilla and eMudhra.

Mozilla then recovered the keys on its own, in under two hours, without knowing Wayne's method. That confirmed the flaw was real and trivial to exploit.

How fast the world reacted

The response was quick:

  • Oct 17: Chrome blocked the six TLS intermediates through its CRLSet mechanism, which needs no browser update. Firefox blocked them within hours.
  • Oct 18: eMudhra revoked all eight intermediates, citing CA compromise. The company says it did this within 14 hours of finding out.
  • Oct 19: Apple added protections, and Cloudflare began patching its services.
  • Oct 20: Microsoft followed, and Mozilla published the incident publicly. Mozilla also removed the parent root, emSign ECC Root CA – G3, from its trust list, and Google announced it would do the same in Chrome, effective October 27.
  • Oct 22: eMudhra's board decided to exit the global TLS certificate business entirely. The company says it was about 1% of revenue, and cited the fallout alongside the economics of free certificates and ever-shorter certificate lifetimes.

eMudhra has since appointed KPMG as an independent external reviewer, and has said it will re-verify every key ceremony it has ever run.

What it actually means

Not everything is on fire. Chrome said none of the six TLS intermediates had any certificate logged in public Certificate Transparency (CT) logs before it blocked them. Browsers that enforce CT logging would have rejected any forged certificate anyway. Cloudflare saw no sign of active exploitation. India's IT ministry (MeitY) says the Indian impact is very limited and that eMudhra's Indian Digital Signature Certificates and eSign services are unaffected, because this concerns its separate international business. So there's no evidence that anyone's bank details or personal data were stolen.

But it's still a serious failure. For a year and a half, eight keys that could mint trusted certificates were effectively public. Software that ships its own trust store (containers, appliances, embedded devices, older Java apps) can keep trusting those intermediates until someone updates it. A forger could also have created fake certificates without ever asking eMudhra for one, so "none were issued" is reassuring but not the whole story.

It raises accountability questions. eMudhra's whole business is trust, and the only real penalty so far has come from the browsers. In India, MeitY formed a team to investigate and CERT-In issued an advisory four days after the report. Legal experts quoted by Inc42 say the IT Act's penalties are dated and that the heaviest lever, licence revocation, would hit the Indian signing business that didn't fail. There's also a reputational cost: if Indian websites end up relying mostly on foreign CAs, India loses a trusted homegrown option.

How to protect yourself

If you're an everyday user:

  • Keep your browser and operating system updated. The blocks reached most people automatically, but updates matter for the rest.
  • If your browser shows a full-page certificate warning, don't click through. Treat it seriously, especially on banking or login pages.
  • If you use eMudhra for a Digital Signature Certificate or eSign in India, MeitY says those services are unaffected. That is currently based mostly on the company's account, so watch for the independent review's findings.

If you run a website or IT systems:

  • Check whether you use emSign certificates, particularly anything chaining to the G3 root. Chrome has removed it, so affected sites show warnings. Move to another trusted CA now.
  • Inventory your trust stores. Look beyond browsers, at payment gateways, vendor integrations, mobile apps, network appliances, containers, and older Java apps. Many of these carry their own CA bundles.
  • Check code signing. Two of the eight keys were for code signing, so audit pipelines and release artifacts for eMudhra-issued certificates.
  • Turn on strict revocation checking where it's currently optional.
  • Monitor Certificate Transparency logs for your domains and alert on unexpected issuers. This is how this incident's exposure was limited.
  • Don't rely on a single CA. eMudhra itself is now offering enterprise customers certificates from an additional authority to avoid a single trust chain.

The bigger lesson

The scariest part of this story isn't a clever attack. It's a simple mistake that survived two audits and sat in plain sight for 18 months until one researcher checked. The padlock is only as trustworthy as the least careful CA behind it, which is why independent researchers, public transparency logs, and browser makers willing to pull trust within hours matter so much.

The story is still developing. The KPMG review and the Indian regulatory response are both pending, so I'd expect more details to emerge.

Sources: