eMudhra exits TLS certificate business after weak-key disclosure, roots still trusted

eMudhra said on October 22 that it is leaving the global SSL/TLS certificate business. The decision comes days after a disclosure that eight of the certificate authority's intermediate private keys were trivially weak — and, according to an analysis published on dev.to, the announcement has so far changed nothing in the trust stores that browsers and operating systems rely on.

What the company said

In its press release, eMudhra says it revoked the affected CAs within 14 hours of discovering the problem, that no end-entity certificates were issued from the affected CAs, and that its infrastructure was not compromised and no data was breached. The company frames the exit as a business calculation: SSL/TLS represents roughly 1% of global revenue, compliance costs are climbing, large competitors hand out certificates for free, and the online scrutiny the incident attracted was, in the company's telling, out of proportion to TLS's share of its business.

The release also commits to a transition plan: the G1 RSA roots keep serving customers until the move is finished, affected customers receive free replacement certificates through partners, and revocation and status services continue until every issued certificate expires or is replaced. A root-cause report to the browser root programs is still outstanding.

The keys behind the exit

The trigger was a mid-October disclosure that eight eMudhra intermediate private keys were positive integers smaller than 256. A dev.to write-up published October 20 reports recovering all eight in 11 milliseconds, with the largest being 237 — a range small enough to enumerate by hand. Six of the keys belonged to TLS intermediates; two to code-signing intermediates.

The working hypothesis from the incident discussion, as relayed in the dev.to post, is that a key wrap/unwrap test produced a second, weak key pair with a label similar to the real one, and the wrong key ended up in the certificate signing request. That account remains unconfirmed until the promised root-cause report lands.

What has actually changed

The dev.to analysis probed the three places where a CA exit would have to become real, and found the picture mixed:

• Trust stores: the Ubuntu CA bundle (ca-certificates 20260816, 121 roots in total) still ships all three eMudhra roots — emSign ECC Root CA - C3, emSign Root CA - C1 and emSign Root CA - G1. That is by design, since pulling a root before customers migrate would break sites that depend on it, but it means the practical trust state is the same as it was before the keys became public knowledge.
• Mozilla's OneCRL: of 1,907 records fetched, six block the compromised TLS intermediates — the DV, OV and EV CAs in both the G3B and G3C generations — by public key, so Firefox rejects anything chaining to those keys regardless of which certificate presents them. The two compromised code-signing intermediates are absent because OneCRL covers TLS; code-signing trust runs through separate stores. A further 20 issuer-and-serial entries exist for certificates under emSign roots, but those accumulate over years and cannot all be tied to this incident.
• The incident record: Mozilla's Bugzilla ticket for the intermediate key compromise, opened October 18, was still in ASSIGNED status and was updated hours after the exit announcement.

Why it matters

A CA leaving the business is a press release, not a technical event. Distrust unfolds through root-program process: roots stay trusted while customers migrate, revocation lists block specific keys, and incident tickets stay open until a root-cause report arrives. The economics here are also instructive — TLS was around 1% of eMudhra's revenue while carrying the full audit, logging, disclosure and reputational weight of running a publicly trusted CA, and that trade collapsed in public view within days.

For organizations holding emSign-issued certificates, the practical guidance from the release is straightforward: the company says it will contact affected customers, replacements through partners are free, and status services keep running until each certificate expires or is swapped out. Until the root programs receive an explanation of how production intermediates ended up with keys anyone could factor, the record stays open even as the business closes.