Latest

Cybersecurity

eMudhra exits global SSL after security blow

eMudhra leaves the global SSL/TLS business after the blocking of eight certificates. It accounted for 1% of its revenue and has cost it 36% on the stock market.

eMudhra exits global SSL after security blow
eMudhra exits global SSL after security blow

eMudhra's board decided on this 22 October 2026 to withdraw from the global SSL/TLS certificate business, and did so five days after Google, Mozilla, Apple and Microsoft blocked eight of its intermediate authorities. The decision contains a paradox worth examining closely: that line contributed around 1% of the company's global revenue and had not issued a single end-entity certificate to a customer, according to the company statement.

V. Srinivasan, chairman of the Bengaluru-based firm, argues in that text that the company revoked the affected authorities within 14 hours, that no one entered its infrastructure and that there was no data leak. He adds two business reasons: the cost and complexity of meeting sovereignty requirements in dozens of countries rose every year, and several giants give the certificate away for free, so the return on that activity narrowed against the rest of the portfolio. The statement also says, bluntly, that amplification on social media brought scrutiny disproportionate to the real weight of SSL/TLS.

What remains is not a cryptography problem but a reputational accounting one. In a business that sells trust, a line that bills little can concentrate the risk of the entire brand. Customers have a runway until 2040 and the other authorities are watching the precedent.

What the company maintains and what is already public

The statement's account is consistent with what is known, although the order of events qualifies one of its phrases. The browsers did not wait for the revocation: Chrome blocked the six TLS intermediates via a CRLSet at 19:45 UTC on 17 October, less than two hours after the private report, and Firefox received the OneCRL list at 22:59. The formal revocation of all eight came the following day, at 09:38 UTC, as we reported in the chronicle of that weekend.

A broken script at the ceremony

The origin is also documented. The keys were born on 30 April 2025 in a ceremony that generated 24 intermediates and, according to the company itself, a wrap-and-unwrap step produced a second set of weak keys alongside the strong ones. Those were the ones that entered the trust stores. The Mozilla ticket and the Cisco Talos analysis leave little room for interpretation.

They were integers below 256 on a P-384 curve, recoverable by computing the 255 possible points on the curve; researcher Scott Helme found that one of them was directly the number 4.

A 1% business that cost 36% on the stock market

The market did not measure the weight of the line, it measured the crack. The shares went from 540 rupees on 19 October to 432 on the 21st, 20% less, and fell another 20% on the 22nd to 345.60, a 52-week low. That is 194.40 rupees per share in two sessions, 36% of market capitalization, and an ongoing investigation by India's Ministry of Electronics and Technology, which set up a special team.

Management described the episode as an isolated incident and stressed that Indian operations are not affected, an argument that CNBC TV18 picked up. The financial part of the argument holds: if the activity contributes 1% of revenue and requires compliance in 35 countries, exiting is cheap for the income statement and expensive for the narrative. The reputational part is not resolved with arithmetic, and there lies the detail that matters for any trust service provider.

What happens to customers until 2040?

The transition has a long calendar and concrete rules. The G1 RSA roots will remain in service until the handover is complete, the company will offer free replacement through its partners, and revocation and certificate status services will keep working until the last issued certificate expires or is replaced.

eMudhra also commits to delivering the full root cause report to the browser programs, the piece still missing to close the file and explain how a ceremony generated one-byte keys.

The tail that lasts until 2040

The problem lives in the tail. The affected certificates do not expire until 28 April 2040, and the browser block only reaches stores that are updated. Languages with their own trust store, Linux distributions without refresh, containers with old images and frozen firmware on industrial equipment keep accepting those chains until someone touches them. Anyone with internal services speaking TLS behind the scenes should review the inventory before the provider changes hands.

A message to the market about trust

The exit reduces supply in a market that was already short. The authorities that browsers accept can be counted on the fingers of two hands, so each withdrawal leaves customers with fewer alternatives and the root programs with more relative weight: in practice, Google, Mozilla, Apple and Microsoft act as de facto regulators of the infrastructure, without going through a parliament and with deadlines measured in hours.

It also orders the priorities of any provider. The company retains digital signature, eSign, PKI platforms and identity products, which do not share infrastructure with SSL/TLS. That is the part of the statement that sounds like strategy and not retreat.

One question remains that the statement does not answer: if the incident was caused by a script failure at a ceremony, what changes in the procedure so that it does not happen again in the lines that remain. The root cause report promised to the browser programs should answer it, and its publication will be the real test of whether the exit was a decision about focus or a way to close the door before someone asks more.

For customers, the message is prosaic and urgent. A certificate that validates until 2040 does not expire when the provider leaves, and no press release replaces an inventory of what trusts what. Trust is bought once and lost in two stock market sessions.

José Maldonado

Author

José Maldonado

Activist and blogger on technology, free software and blockchain.

The latest
From Huang to Botín, from Zara to Byron: corporate responsibility in global capitalism

Keep reading