eMudhra Will Exit Public TLS Certificates; G3 Is Distrusted, G1 Still Issues

eMudhra, the Bengaluru company whose weak intermediate keys prompted Google and Mozilla to distrust part of its certificate hierarchy, plans to wind down its global SSL/TLS certificate business. According to a company filing cited by Inc42, the segment is about 1% of global revenue, against ₹701.6 crore of total revenue in FY26. Cofounder Kaushik Srinivasan said "the impact has been quite severe over the last 24-48 hours."

The decision follows an October 17 report from a researcher identified only as Wayne, who notified the browser root programmes and eMudhra that the private keys of eight intermediate certificate authorities were recoverable. This piece covers what the wind-down does to customers rather than the cryptography.

Which eMudhra roots are affected

eMudhra runs two root hierarchies, G1 on RSA and G3 on ECC, according to Inc42. Google and Mozilla distrusted G3 as a precaution. G1 continues to operate and issue certificates.

Hierarchy	Algorithm	Status
G1	RSA	Operating and issuing
G3	ECC	Distrusted by Google and Mozilla

All certificates in India and nearby markets were issued from G1, Srinivasan told Inc42. G3 distrust hit about 30,000 certificates belonging to an undisclosed US client, which he said were moved to RSA and are now being transitioned to another provider. CSO Online quoted Yash Kadakia, founder and chief technology officer of Security Brigade, estimating that about 30,000 legitimate certificates would need migrating. The two accounts of the 30,000 figure come from different people and may not describe the same set.

What eMudhra says it will do

Existing customers will be moved to other providers free of charge over three to four weeks, per Inc42. eMudhra will appoint an auditor to prepare a final report, which Srinivasan estimated at two to three weeks. Promised controls include maker-checker approval, independent review of critical processes such as key generation, and "AI-based checks" to flag errors.

eMudhra gave commercial reasons for leaving alongside the incident. Inc42 reports it cited rising compliance costs, declining returns and weak prospects, with Let's Encrypt and a planned free Cloudflare offering limiting pricing and browser moves toward 90-day certificates adding cost. Srinivasan said the board "evaluated the social media reaction" as well as return on investment.

The audit gap

The intermediates were created on April 30, 2025, and had passed independent audits, Inc42 reports. The flaw went unnoticed for about 18 months across two audit cycles, and eMudhra did not name the auditors or the scope. Researcher Scott Helme, who published the key values, put the window at 17 months.

Srinivasan attributed the fault to a script error and human oversight and called it "a one-off, a bad day." Inc42 reports that security experts were not satisfied with that explanation. Mozilla engineer Dennis Jackson called the key generation process flawed and "trivial to exploit," per CSO Online, and Mozilla shipped Firefox 158.0.1 and NSS 3.131.1 on October 20 to extend the block.

What customers should check

Anyone holding an eMudhra TLS certificate should confirm which hierarchy issued it. A certificate chaining to G3 is already blocked in Firefox and Chrome. G1 continues to operate, but eMudhra says it will migrate customers to other providers over the next three to four weeks, so plan the reissue rather than waiting for the notice.

For other disclosures with fixed versions, see the Plex2Shell four-CVE advisory and the Next.js 16.4.1 advisories. eMudhra's final audit report is due in two to three weeks.