eMudhra board exits global SSL/TLS certificate business after weak keys
Indian certificate authority eMudhra said on 22 October 2026 its board decided to withdraw from the global SSL/TLS certificate business, which brings in about 1 percent of its global revenue, after eight weak private keys surfaced.
Photo: The RegisterKey points
eMudhra's board decided to withdraw from the global SSL/TLS certificate business, which contributes about 1 percent of its global revenue, after eight weak private keys were exposed.
Indian certificate authority eMudhra said on 22 October 2026 that its board had decided to voluntarily withdraw from the global SSL/TLS certificate business. The segment brings in about 1 percent of the company's global revenue. The announcement followed public reports that exposed weak private keys, one of which was the single digit 4.
The decision matters because eMudhra's certificate authority infrastructure had been in browser trust lists since mid-2025, and the weak keys belonged to eight intermediate certificate authorities. Those intermediates could have let attackers forge certificates trusted by systems that had not blocked them. eMudhra said the affected authorities had issued no end-entity certificates, so no forged certificates reached the web.
What the board decided
eMudhra said growing compliance costs, data sovereignty requirements, and competition from free certificate providers had made the business hard to justify. The company also said the attention around the incident was out of proportion to the segment's size. "The level of social media amplification around this incident has brought scrutiny that is out of proportion to SSL/TLS's place in our business," eMudhra said.
The eight affected private-key values were small numbers: 4, 56, 66, 115, 155, 156, 230, and 237. Security researchers recovered them without special tools. The weakness was reported to Mozilla on 17 October, and public reports followed two days later. A private key is the secret number that proves a certificate authority's identity; keys this small can be guessed rather than cracked.
eMudhra said a flaw in its key-generation ceremony produced the weak keys alongside the intended strong ones. "A flaw in the key generation ceremony caused a wrap/unwrap step to produce a second set of weak keys alongside the original strong keys," the company said. "The weak keys were the ones published to the browser root stores."
How the weak keys happened
The company said the affected certificate authorities had been in browser trust lists since mid-2025 and had undergone two years of independent audits, which raises the question of why the weak keys were not caught sooner. eMudhra said it revoked the affected authorities within 14 hours of discovering the issue and disclosed the problem to relevant stakeholders.
Chairman V. Srinivasan said the incident did not lead to unauthorised certificate issuance or a breach of customer information. "There were no end entity certificates issued out of the affected CA's. Its infrastructure was not compromised, no data was breached All physical and logical security controls remained intact," the statement said. eMudhra also said its infrastructure and data were not compromised.
The board weighed the compliance burden against the segment's small revenue contribution before deciding to stop. eMudhra said the withdrawal would let management focus on areas with stronger growth potential and reduce complexity and compliance obligations. The company did not give a specific timeline for completing the withdrawal or details about transition arrangements for existing customers.
eMudhra said it will keep serving G1 RSA roots until it moves customers to other certificate issuers, which it will do free of charge. It also said revocation and certificate status services will keep running until every issued certificate has expired or has been replaced. The company said it will still issue a root-cause report and meet its remaining commitments to browser root programs.
The incident gives eMudhra a second reason to shrink a small part of its business rather than keep facing scrutiny over its certificate operations. The company said the scrutiny followed reports that showed weak private keys, one of which was just the number 4, at eight intermediate certificate authorities trusted by browsers.
eMudhra's withdrawal removes one certificate authority from the global market at a time when browsers already blocked eight of its certificates. The company said free SSL/TLS certificate issuance from large firms and increased compliance and data sovereignty requirements had made the segment a minor part of its operation. The next step is eMudhra's root-cause report and its transition of customers to other certificate issuers, which it said it will carry out free of charge. The company did not publish a date for the report or for completing the withdrawal, and it did not name the issuers that will take over its customers.
Frequently asked questions
Why is eMudhra leaving the global SSL/TLS certificate business?
eMudhra's board decided to withdraw after public reports exposed weak private keys. The company said the segment brings in about 1 percent of its global revenue and that rising compliance costs, data sovereignty requirements, and competition from free certificate providers made it hard to justify.
What were the weak private keys at eMudhra?
Eight affected private-key values were 4, 56, 66, 115, 155, 156, 230, and 237. They belonged to eight intermediate certificate authorities. eMudhra said a flaw in its key-generation ceremony produced these weak keys alongside the intended strong ones, and the weak keys were published to browser root stores.
What happens to certificates already issued by eMudhra?
eMudhra said it will continue serving G1 RSA roots until it moves customers to other certificate issuers, free of charge. Revocation and certificate status services will keep running until every issued certificate has expired or has been replaced.


