eMudhra’s board decided on October 22 to withdraw from the global SSL/TLS certificate business, five days after a researcher reported recovering the private keys for eight of its intermediate CA certificates. Google plans to distrust one of its roots in Chrome from October 27, and Oracle issued an out-of-band Java alert the same day.
eMudhra’s Decision to Leave the TLS Certificate Market
Six of the eight compromised intermediates were TLS certificates. eMudhra said it will replace affected customers’ certificates with free ones from unnamed partners but gave no date. The company will keep revocation and status services running until all of its TLS certificates have expired or been replaced. Digital signature, eSign and the CertiNext platform continue to operate, and eMudhra said the TLS business accounts for about 1% of its revenue.
The Company’s Explanation of the Weak Keys
According to The Register, eMudhra attributed the problem to a flaw in its April 30, 2025 key generation ceremony, which used FIPS 140-2 Level 3 hardware security modules. The company said the flaw produced a second set of weak keys, and that those were the ones published to browser root stores. It pointed to two years of clean audits. One key was reportedly the number 4.
Chrome Sets Its Distrust Date for the ECC G3 Root
Chrome will stop trusting the root “emSign ECC Root CA – G3,” with the change expected to reach users on the morning of October 27, Pacific time. Mozilla decided on October 20 to stop trusting the same root in Firefox. Google told site operators that they “must immediately acquire and install a new TLS certificate.”
About 30,800 unexpired certificates chain to that root, based on a certificate transparency log count from October 21. Roughly 99.9% were issued through InCommon, the higher-education certificate service, which moved onto eMudhra’s CertiNext platform between April and July. The concentration means universities and other education sites carry most of the replacement work.
Status of the G1 RSA Roots
eMudhra’s G1 RSA roots remain in service for now. Chrome is still deciding what to do about them, so the distrust decision covers only the ECC G3 root at this stage.
Oracle’s Out-of-Band Java Alert for CVE-2026-91403
Oracle released an out-of-band Java alert for CVE-2026-91403, rated CVSS 9.1, which distrusts the compromised intermediates in Java SE and GraalVM. The change applies to the JSSE component. Oracle has not reported exploitation, and the flaw is not in the CISA Known Exploited Vulnerabilities catalog.
Other runtimes have acted as well. Go added blocks on October 20, and Node.js did so in its October 21 release, according to The Hacker News. Together with the browser decisions, the actions remove trust for the keys across the main client platforms that handle web certificates.
Forged-Certificate Risk Until Trust Stores Update
Because the private keys for the intermediates were recovered, the concern is that someone holding them could issue convincing certificates for sites. That risk persists on any client that has not yet applied a distrust update. The staggered timing of the actions, from Go and Mozilla earlier in the week to Chrome on October 27, creates a period in which some clients still accept the roots.
For the thousands of affected sites, a replacement certificate from a different authority is required. eMudhra’s promise of free replacements has no schedule attached, and Google’s instruction to operators is to act immediately rather than wait.
What Remains Undecided About eMudhra’s G1 Roots and Partners
Chrome’s ruling on the G1 RSA roots is pending, and eMudhra has not named the partners that will supply replacement certificates. The company’s board decision ends its participation in the global TLS market, but the revocation and status services it promised to maintain will continue to matter until every certificate in circulation has expired or been swapped out.
