Bengaluru-based digital trust authority eMudhra Limited announced on Saturday its voluntary departure from the global SSL/TLS certificate market, a stunning move for the global Public Key Infrastructure (PKI) ecosystem. The decision came after a massive cryptographic flaw in which eight of its intermediate Certificate Authority (CA) keys proved frighteningly predictable—so much so that reports say key entropy was so broken, one key was as easy to predict as the number 4.
Over the next five days, major browsers (Google Chrome, Mozilla Firefox, Apple Safari and Microsoft Edge) reacted rapidly in blocking these weak intermediate certificates while leading root stores expedited their distrust timelines. With investor confidence in free fall, a 20% drop in stock upon market open, and severe business challenges ahead resulting from the unplanned exclusivity period for certain key SSL products, eMudhra’ s board chose to step away completely from the public web security space.
This event reflects global digital trust fragility, the importance of key generation ceremonies and the urgency for enterprise Crypto Agility.
In this post, we look at what went wrong: Specifically, a botched key generation ceremony.
The failure was centered on a key-generation ceremony that occurred on 30 April 2025. Key ceremonies are the supposed hyper encryption ritual, performed at secure Facilities utilizing HSMs under multi-party physical and logical controls to create high-entropy root and intermediate keys.
┌─────────────────────────────────────────────────────────┐
│ April 30, 2025 Key Ceremony │
└────────────────────────────┬────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────┐
│ Flaw in Key Wrap / Unwrap Processing Logic │
└──────────────┬───────────────────────────┬──────────────┘
│ │
▼ ▼
┌───────────────────────────┐ ┌───────────────────────────┐
│ Strong Key Set │ │ Predictable Key Set │
│ (Kept in HSM Storage) │ │ (Published to Root Stores) │
└───────────────────────────┘ └────────────┬──────────────┘
│
▼
┌───────────────────────────┐
│ 8 Weak Intermediate CAs │
│ (6 TLS / 2 Code-Signing) │
└───────────────────────────┘
As per technical disclosures made by eMudhra, the failure was procedural and technical in nature during cryptographic “wrap/unwrap” processing steps. However, this malfunction led the ceremony to produce two pair of keys
A solid cryptographically-secure private key pair, stored in local HSM memory.
A secondary set of keys, which are grossly compromised as they were generated with close to zero entropy or randomness.
The secondary weak, and dare I say it, easily guessable key set was published directly in global browser root stores to boot. Of eight impacted intermediate CAs, six were for public website SSL/TLS certificates and two were for code signing.
Public key cryptography depends on the fact that it is mathematically impossible to guess a private key from its public pair, but publishing a key with very little entropy alone effectively allowed whoever calculated it to forge authentic digital signatures.
Browser Escalation & Emergency Revocations
The response across the cybersecurity community was swift, once independent security researchers discovered the weak keys and disclosed them publicly in mid-October 2026.
An Intermediate CA has the power to produce certificates that can be accepted by default from millions of devices around the world. If an attacker is able to control or guess a single intermediate private key, they can successfully conduct Man-in-the-Middle (MitM) attacks, decrypt encrypted HTTPS web traffic, and host seemingly perfect fake corporate sites that still passed the browser security checks without causing so much as warning.
Timeline of the Fall
- October 17, 2026: Emergency Blocks on the six TLS-issuing intermediate CAs Implemented by Google Chrome and Mozilla Firefox
- October 20, 2026: Mozilla has decided to remove trust from eMudhra’ s messing ECC Root CA – G3 root in Firefox
- October 21, 2026: A high-severity security advisory on the key flaw is issued by India’s CERT-In (Computer Emergency Response Team).
- October 22, 2026: Chrome announces mistrust of the emSign ECC Root CA – G3 root, leaving no time for site operators to re-issue certificates. On that day, the eMudhra board ultimately votes to withdraw from the global public SSL/TLS market.
Timeline of Events (October 2026)
───────────────────────────────────────────────────────────────────────────
17 Oct ► Chrome & Firefox deploy blocklists against 6 weak intermediate CAs.
Oct 20 ► Mozilla revokes trust for emsigner ECC Root CA – G3
Oct 21 ► CERT-In BJP files ruckus in Maharashtra Assembly over alleged phone tapping by police
22 Oct ► Google Chrome final distrust date confirmed; eMudhra exit
───────────────────────────────────────────────────────────────────────────
Despite eMudhra providing assurances that none of the 8 intermediate CAs had ever issued end entity certificates for public websites, major browser vendor root store policy is unforgiving; a severe cryptographic failure at a CA key ceremony voids the core promise of public trust.
Financial and Operational Collateral Damage
Approximately ~1% of eMudhra’ s overall global revenue came from Public SSL/TLS certificates, but the public relations and market fallout was immediate.
Financial and Operational Collateral Damage
While public SSL/TLS certificates accounted for only ~1% of eMudhra’ s overall global revenue, the public relations and market fallout was instantaneous:
| Impact Metric | Status / Value |
|---|---|
| Stock Market Response | Shares dropped 20% to lower circuit limits on Indian exchanges (BSE/NSE). |
| Affected Certificates | Over 30,800 active web certificates lost trust across global systems. |
| Primary Industry Impacted | Higher Education (Internet2 / In Common ecosystem). |
| Unaffected Business Units | Enterprise PKI (emCA), eSignature (emSigner), local Indian eSign, & Identity platforms. |
SSL/TLS is the only business for many certificate authorities. This is merely one aspect of eMudhra’s wide-ranging portfolio for digital transformation. “Exiting was the most sensible route ahead given increased regulatory compliance costs, unwieldy operational overhead and competition from free certifications.”
V Srinivasan, chairman, eMudhra
So, who fell victim to this sudden departure? Enterprise networks in the institutions endeared primarily benefiting. More than 99.9% of all existing certificates associated with the compromised ECC root from eMudhra were issued for North American universities using Internet2’s InCommon Certificate Service. Hundreds more internal domains, portal systems and server endpoints received browser invalidation warnings overnight at educational institutions including Cornell Stanford and the University of Michigan.
Industry Takeaways: Crypto agility is a must!
eMudhra’s departure resembles similar events when multiple major PKI vendors including Symantec and Entrust were deprecated by Chrome in the past. But while previous CA deprecations took months or years to play out, the exit by eMudhra happened in less than a week.
Evolution of CA Distrust Timelines
Symantec (2017) │ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ █ (12-18 Months)
Entrust (2024) │ █ █ █ █ █ █ (6 Months)
eMudhra (2026) │ ▌ (5 Days)
└──────────────────────────────────────────────
This rapid escalation highlights four key takeaways for security architecture:
Mandatory Key Generation Automated Verification
The days of just relying on procedural compliance with air gapped key generation ceremonies are coming to an end. Executive Summary: Every automated validation tool for cryptographic material must have the capability to inline on-line exhaustive real-time entropy verification and public key parameters, along with measurable mathematical proof that the keys themselves strictly conform, live, with a global NIST/RFC standard as a necessary prerequisite to any publicly-registered certificate chains.
Shrinking Certificate Lifespans Require Automation
Do you store all digital keys and release dates in a spreadsheet and wait until the next month to replace them? However, those organizations that had previously deployed Automated Certificate Management Environment (ACME) protocols were able to transition their public certificates with little friction as they moved to backup CAs in the incident whereas manual deployments required a considerable amount of work.
Establish Multi-CA Redundancy
Cons of Single PKI Vendor: The major disadvantage of single PKI vendors is that a single point will fail. For enterprise threat-modeling these days, you need to be dual-homed or multi-CA where real-time switches between independent CAs without any loss of uptime are achieved.
Visibility Across Non-Standard Endpoints
But resources are not limited to standard web apps being put at risk by the distrusting of a root cert. When your customer has hard-coded root certificates (root pinning) in local API gateways, container registries, mobile apps and IoT devices you need deep asset discovery to make sure that service outages are not guaranteed availability of everyone.
Conclusion
This leaves eMudhra as the real pioneer and might grant it an edge into what is certain to be the next generation of public key infrastructure. In short, it makes clear that as soon as something goes astray with cryptographic integrity, immediate action will be taken by the root stores and browser vendors.
As eMudhra pivots to an enterprise digital signature and localized identity services and in-house PKI management-only strategy, the rest of the cybersecurity industry would do well to take away the hard-and-fast lesson this incident teaches: Connecting people and things as trusted identities is costly upfront but takes infinite effort to keep around (and can fall over easily without proper, ongoing cryptographic discipline).