eMudhra Exits TLS Certificate Business After Key Flaw

7 min read

Came here from Instagram, LinkedIn, X or YouTube? Here is the full source list you came for. Everything below is built from these, nothing else.

The report and the interview

• Inc42: eMudhra To Exit Certificate Business As Security Flaw Triggers Distrust, October 22 2026

eMudhra, a Bengaluru-based cybersecurity company, is shutting down its global SSL/TLS certificate business. In a filing, it said the decision followed a security incident: a researcher found that the private keys of eight of its intermediate certificate authority (CA) certificates were weak enough to be recovered. Google and Mozilla's browser root programmes then distrusted eMudhra's certificates.

The company says it revoked the affected CAs within 14 hours, that none of them had issued end-entity certificates, and that no data was breached. Existing customers will be moved to other certificate providers free of charge over the next three to four weeks. "The impact has been quite severe over the last 24-48 hours," cofounder Kaushik Srinivasan told Inc42.

Key takeaways

• The private keys of eight intermediate CA certificates were generated with insufficient randomness. Six were meant for TLS and two for software signing.
• eMudhra revoked them within 14 hours, but the flaw had gone undetected for about 18 months, across two independent audit cycles.
• Google and Mozilla distrusted the G3 ECC root as a precaution. Around 30,000 US certificates had to move to the G1 RSA root, and now have to move again.
• The TLS business was about 1% of global revenue, against ₹701.6 Cr in FY26 revenue.
• Customers get a free transition to other providers over three to four weeks. An auditor's final report is due in two to three weeks.

What exactly went wrong with eMudhra's keys?

On October 17, a researcher named Wayne notified the browser root programmes and eMudhra that he had recovered the private keys for eight intermediate CA certificates. The keys had been generated with insufficient randomness, which made them possible to reconstruct.

Here is the short version of how it unfolded, using only what eMudhra and Srinivasan have said:

When	What happened
April 30, 2025	The eight intermediate certificates are created. eMudhra says they went through independent audits, but did not name the auditors or the audit scope.
About 18 months	The flaw sits undetected through two independent audit cycles. Only one of the eight is deployed in production.
October 17	Wayne reports the recovered keys to the root programmes and to eMudhra.
Within 14 hours	eMudhra revokes all eight affected CAs and discloses the incident.
After that	Mozilla and Google block the affected TLS intermediates and distrust the G3 ECC root as a precaution.
October 22	Inc42 reports eMudhra's plan to wind down the TLS certificate business.

Srinivasan's explanation is that it was a script error and a human oversight problem, and that no hardware problem was found. "It was a one-off, a bad day. That's exactly what happened," he said. He also said the facts will be shared in due course and verified through independent research.

Security experts were not satisfied with eMudhra's earlier clarification, according to Inc42. So treat the "one-off" framing as the company's account until the auditor's report lands.

Why does this matter to a developer?

Most of us never think about who signed our certificate. We paste a cert into a load balancer once a year and forget about it. This story is a good reminder of why that is risky.

A recovered intermediate key is a master key

An intermediate CA sits between the root that browsers trust and the certificate on your site. If someone holds an intermediate's private key, they could potentially issue fraudulent certificates for websites or software. Two of these eight were for software signing, so the risk was not limited to HTTPS.

eMudhra says none of the eight had issued end-entity certificates and its infrastructure was not compromised. That limited the damage. It did not stop the browsers from acting.

Audits did not catch it

This is the part I keep coming back to. The keys were created on April 30, 2025. They passed independent audits. They went through two audit cycles. Nobody flagged them for about 18 months, until an outside researcher did.

A key generated with too little randomness does not throw an error. The certificate still works. Everything looks normal until someone tries to rebuild the key and succeeds. A script that does its job "well enough" is exactly the kind of code that never gets a second look.

You can lose trust for something you did not do

Google and Mozilla distrusted the whole G3 ECC root as a precaution. That hit around 30,000 certificates for a US client, according to Srinivasan. Those customers did nothing wrong. Their certificates simply sat under a hierarchy that browsers no longer trusted.

"It resulted in around 30,000 certificates in the US market being affected because they were under ECC. We had to transition them to RSA. Following our announcement, we have to transition them to another provider," he said.

So those certificates move twice in a matter of weeks. If you run anything at scale, that is two rounds of reissuing and redeploying.

Paid TLS certificates are a shrinking business

The exit was not only about the incident. Srinivasan pointed to rising compliance costs, declining returns, and limited revenue. The segment was about 1% of global revenue. He also said the commercial return looks limited with Let's Encrypt offering free TLS certificates, Cloudflare planning to do the same, and browser guidelines moving towards 90-day certificates.

"The board evaluated the social media reaction, but also took cognisance of the ROI, future potential and competitive landscape," he said. eMudhra plans to focus on its core enterprise business and on harder problems in areas like AI and quantum computing.

For you, that means the default for a public website keeps moving towards free, short-lived, automated certificates.

What changes in practice?

If you are an eMudhra TLS customer, you will be moved to an alternative provider free of charge over the next three to four weeks. eMudhra says it is working with other certificate partners to avoid service disruptions.

If your certificates were in India or nearby markets, they were issued from the G1 RSA root, according to Srinivasan. G1 continues to operate and issue certificates. You are not under the distrusted G3 root, but you are still on a provider that is leaving the business, so you will still need to move.

If you were one of the US certificates under G3, you have already been moved once, from ECC to RSA. You will be moved again to another provider.

If you use any CA at all, the shift towards 90-day certificates means manual renewal stops being practical. Four renewals a year per domain is a lot of calendar reminders to trust.

If you write scripts that generate keys or secrets, this is your case study. eMudhra says it will tighten internal accountability, add maker-checker controls and independent reviews for critical processes like key generation, and explore AI-based checks that flag weaknesses and potential errors. None of that requires a certificate authority's budget.

What should you do this week?

1. Find out who issued your certificates. Run this against each domain you own and read the issuer line:

openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null \
  | openssl x509 -noout -issuer -enddate

2. If the issuer is eMudhra, get a date. The company says the move takes three to four weeks. Ask your account contact which provider you are going to and when, so you are not finding out from an expiry alert.

3. Automate renewal now, not later. With browser guidelines moving towards 90-day certificates, a renewal you have to remember is a renewal you will eventually miss. Let's Encrypt already offers free TLS certificates, so cost is not the blocker.

4. Read your own key generation code. Open every script that creates a key, a token, or a secret. Find the exact line where the randomness comes from. If you cannot point to it, that is the bug to fix first.

5. Put a second person on anything that mints keys. That is what maker-checker means: one person writes it, another checks it before it runs. eMudhra is adding this after the fact. You can add it before.

6. Keep a list of where every certificate lives. When a root gets distrusted, the slow part is not getting a new certificate. It is finding every server, CDN, and app that uses the old one.

7. Watch for the final report. Srinivasan says an auditor will prepare it, and it should take two to three weeks. It should say what the script error actually was.

FAQ

Why is eMudhra exiting the TLS certificate business?

A researcher recovered the private keys of eight intermediate CA certificates, and Google and Mozilla then distrusted eMudhra's certificates. The company also cited rising compliance costs, declining returns, and the segment's small share of revenue, about 1%. Free certificates from Let's Encrypt and the move towards 90-day certificates were part of the reasoning too.

Are eMudhra certificates still trusted by browsers?

Google and Mozilla distrusted the G3 ECC root as a precaution and blocked the affected TLS intermediates. The G1 RSA root continues to operate and issue certificates, and all certificates in India and various adjoining markets were issued from G1. eMudhra is still moving every existing customer to another provider.

Was any customer data breached?

eMudhra says no. It says the affected CAs never issued end-entity certificates, its infrastructure was not compromised, and no data was breached. An auditor's final report on the incident is expected in two to three weeks.

What caused the weak keys?

The keys were generated with insufficient randomness, which made them possible to reconstruct. Srinivasan described it as a script error and a human oversight problem, with no hardware problem found. The flaw went undetected for about 18 months across two independent audit cycles.

Run the issuer check on your domains today, then use the free tools on Art of Code for the rest of your dev chores. If security work like this interests you, browse the latest openings on Art of Code Jobs.

Written by Adithya Guttha, Founder of Art of Code.