eMudhra, the Mumbai-listed certificate authority, said on October 22, 2026 that its board decided to voluntarily withdraw from the global SSL/TLS certificate business, according to The Economic Times. The decision follows the discovery of weak private keys inside eight intermediate certificate authorities that browsers had trusted.
The exit arrives just five days after a researcher flagged the problem on October 17. By October 20, Google Chrome, Mozilla Firefox, Apple Safari and Microsoft Edge had all moved to block the affected certificates. TNW reported that the company framed the withdrawal as a business call as much as a security one, since the global TLS unit is a small slice of a much wider portfolio.
We covered the cryptography first in our report on the eMudhra CA keys, one of which was the number 4. This piece looks at what the exit means for eMudhra, for the certificate market, and for any team that still has an eMudhra-issued certificate on a production endpoint.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What eMudhra Announced on October 22
eMudhra Limited (NSE: EMUDHRA, BSE: 543533) told the market that its board chose to leave the global SSL/TLS business entirely. The company said it withdrew eight certificates, that its infrastructure was not compromised, and that no data was breached. Those claims come from the company’s own statement as relayed by The Economic Times, and independent verification of the infrastructure claim is not available in the public record yet.
The affected assets are eight intermediate certificate authorities used in eMudhra’s global TLS operation. An intermediate CA sits between a trusted root and the certificates that websites actually present to visitors. Whoever holds an intermediate’s private key can mint certificates for any domain that browsers will accept, which is why a weak key at that level is treated as a trust emergency rather than a routine bug.
India’s Computer Emergency Response Team, CERT-In, issued an advisory stating that some eMudhra intermediate certificates were compromised. The Economic Times cited that advisory directly in its coverage of the announcement. eMudhra’s own wording is narrower. It says the keys were weak because of a flaw in how they were generated, and it denies any intrusion into its systems.
One more point of care. The headline framing that eMudhra left “after vulnerability disclosure” is a reasonable shorthand, but the available reports only establish that the exit followed the incident. They do not show that the disclosure alone forced the decision. The company itself pointed to cost, compliance burden and the scale of public scrutiny.
Timeline: From a 2025 Key Ceremony to a 2026 Exit
The sequence matters because it shows how long a weak key can sit unnoticed. The flawed key-generation ceremony took place on April 30, 2025. The problem surfaced about 18 months later, on October 17, 2026. Once it did, the response moved quickly, at least on paper.
| Date | Event | Reported by |
|---|---|---|
| April 30, 2025 | Key-generation ceremony, where a wrap/unwrap step produced a second set of weak keys | eMudhra statement, via TNW |
| October 17, 2026 | Researchers identify weak keys in eight intermediate CA certificates | Business Today |
| About 14 hours after discovery | eMudhra revokes the affected certificate authorities | TNW |
| By October 20, 2026 | Chrome, Firefox, Safari and Edge block the affected certificates | TNW |
| October 21, 2026 | eMudhra publishes a root-cause statement, India’s IT ministry says it formed a special team | TNW, Business Today |
| October 22, 2026 | Board announces voluntary exit from global SSL/TLS | The Economic Times |
Fourteen hours from discovery to revocation is fast by industry standards, and eMudhra leans on that number in its defense. The harder question is the 18 months before discovery. During that window the weak keys sat in browser root stores while nobody outside the company, as far as public reports show, knew they were there.
How Weak Keys Reached the Browser Root Stores
A flaw in the key-generation ceremony
eMudhra’s explanation is specific. In its published statement, the company said: “A flaw in the KGC caused a wrap/unwrap step to produce a second set of weak keys alongside the original strong keys. The weak keys were the ones published to the browser root stores.” KGC stands for key-generation ceremony, the scripted, witnessed procedure a CA uses to create the keys that anchor its trust.
In plain terms, the ceremony produced two key sets. One was strong. The other was weak, and the company says the weak set was the one published to the browser root stores. Keys that sit in a public trust store are keys an attacker can study.
Why 3 to 8 bits breaks the trust model
According to reporting that cites the security researcher’s finding, the affected private keys had an effective key space of just 3 to 8 bits. A key space of 8 bits means 256 possible values. A laptop tests that many guesses in well under a second. Modern elliptic-curve and RSA keys are meant to resist guessing across ranges so vast that the comparison is not meaningful.
TNW added a detail that made the finding easy to grasp. One of the private keys was the number 4. A key that small cannot protect anything, and anyone who checked the public certificate data could in principle derive it. The company also said that the certificate authorities passed independent audits two years in a row, and that an independent researcher worked the keys out, possibly using AI-assisted techniques. That claim is the company’s, and no outlet has independently confirmed the method.
How Chrome, Firefox, Safari and Edge Responded
All four major browser vendors moved to block the affected certificates by October 20, 2026. That coverage matters more than any single vendor’s action, because a CA that loses one major root program is damaged, while a CA that loses all four loses its usefulness for public web trust.
Business Today reported that Google went further than a block. It announced measures to block the compromised intermediates in Chrome and planned to remove the associated emSign ECC Root CA G3 certificate from its trust store. Mozilla, Apple and Microsoft also acted to block the affected certificates, according to the same report.
The practical effect for site owners is blunt. Business Today noted that legitimate websites using the affected certificate chain could see security warnings or connectivity problems until they move to replacement certificates. For an e-commerce checkout page or a login portal, a browser interstitial is close to an outage.
The speed of the browser response also tells a story. Blocking intermediates by name is a surgical move that browsers can ship quickly through their update channels. Removing a whole root is slower and riskier because it breaks every certificate beneath it, including ones that were issued correctly. That tradeoff explains why the first wave of action targeted the eight intermediates and why root removal is reported as a planned step rather than an instant one.
CERT-In and India’s IT Ministry Step In
The Indian government responded on two fronts. CERT-In issued its advisory on the compromised intermediates. The Ministry of Electronics and Information Technology (MeitY) then said it had taken serious note of the incident and formed a special team to investigate, Business Today reported.
MeitY drew a firm line between eMudhra’s two functions. The first is issuing Digital Signature Certificates and eSign services, which the Controller of Certifying Authorities regulates under the ministry. The second is issuing certificates that browsers and operating systems trust for websites. The ministry said the incident touches only the second. It also described the impact on Indian websites and applications as limited and short-lived, and warned against what it called fear mongering on social media.
Business Today added that the global trust business operates under international standards and independent audits, including WebTrust audits conducted by BDO International Limited. It also stated that as of October 21, public reports had not established widespread attacks using the compromised keys. The outlet cautioned that the absence of confirmed misuse does not rule out exploitation.
India’s security community has had a busy month. Our earlier coverage of the SBI data leak that put 3,897 records on the dark web showed how quickly claims and counterclaims spread after an incident. The eMudhra case follows the same pattern, with a company statement, a ministry rebuttal and social media amplification all landing within days.
What the Exit Means for eMudhra’s Business
The financial exposure looks contained. Co-founder Kaushik Srinivasan said the affected global TLS business accounts for around 1% of company revenue. TNW carried the same figure, and also reported the company’s argument that data sovereignty and compliance rules have made the unit more complex and costly to run.
Srinivasan also said, in comments reported after the announcement: “There’s no impact to subscribers because we have done all the actions.” On the rest of the group, he said: “This does not affect our other lines of business, which is the India digital signature and our enterprise solutions business.”
| Business line | Status after October 22 | Detail |
|---|---|---|
| Global SSL/TLS certificates | Exiting | Around 1% of revenue, eight intermediate CAs withdrawn |
| India Digital Signature Certificates (DSC) | Unaffected | Runs on infrastructure separate from global TLS |
| eSign services | Unaffected | Separate infrastructure, regulated in India under the CCA |
| emCA and CertiNext enterprise PKI | Untouched | Named by the company as continuing |
| emSigner eSignature suite | Untouched | Named by the company as continuing |
| SecurePass and emAS identity products | Untouched | Named by the company as continuing |
The table reflects company statements as reported by TNW. eMudhra also posted a statement on the distrust of its global TLS intermediate and root CAs in its investor materials. The company says it operates in more than 35 countries and trades in Mumbai. None of the reports we reviewed give a revenue forecast change, so any estimate of earnings impact would be guesswork on our part.
Why Walk Away From a 1% Business?
The answer sits in the economics TNW described. Some large players issue TLS certificates for free, which has cut the potential return for paid issuers. Public web certificates are close to a commodity, and the revenue per certificate keeps falling while compliance costs rise. For a company that gets about 1% of its revenue from the line, the compliance overhead can outweigh the margin.
Reputation adds a second pressure. In its statement, eMudhra said the level of social media amplification had brought scrutiny out of proportion to SSL/TLS’s place in its business. That sentence reads as a case for focus. A small unit generated outsized headlines, and those headlines landed on a company whose larger customers buy digital signatures and enterprise PKI, where trust in the brand matters just as much.
Third, there is the remaining workload. TNW reported that eMudhra still owes the browser root programs a full root-cause report and other commitments. Staying in the public TLS business means staying inside that audit and reporting regime for years. Leaving means finishing the existing obligations and then exiting the regime altogether.
What eMudhra Says Happens to Existing Customers
The wind-down plan, as TNW laid it out, has three pieces. First, eMudhra’s G1 RSA roots keep serving customers until the transition is complete. Second, the company is working with the browser programs and will contact affected customers to replace their certificates free of charge through partners. Third, its revocation and certificate status services keep running until every certificate it issued has expired or a replacement is in place.
TNW also reported Srinivasan’s statement that the affected authorities issued no certificates to websites or users. If that holds, the practical blast radius is smaller than the headline suggests, because the compromised intermediates were not the ones signing end-entity certificates that customers deployed. That claim comes from the company and we could not verify it independently, so site owners should still check their own certificate chains.
Market Impact: What Changes for Certificate Buyers
Few enterprises will feel a direct hit, since eMudhra was a minor player in global TLS by the company’s own revenue figures. The market effect is indirect and falls in three places.
- Procurement reviews. Security teams that bought from smaller CAs for price reasons now have a fresh reason to ask about key-generation controls and audit depth.
- Trust-store scrutiny. Browser programs will likely look harder at how key ceremonies are witnessed and verified, since two clean annual audits did not catch this one.
- Consolidation pressure. Small CAs facing free competitors and rising compliance cost now have an example of how a single mistake can end a product line.
The timing problem is the part buyers should absorb. Our report on PHP2Shell attacks that began four days before disclosure showed how exploitation can outrun a public advisory. With eMudhra, no widespread abuse has been established, but an 18-month gap between the faulty ceremony and the discovery is a long window for anyone who spotted the weakness quietly.
Historical Context: How Past CA Failures Ended
Public certificate authorities have a long record of losing trust. DigiNotar collapsed after its 2011 compromise. WoSign and StartCom were distrusted by browsers in the following years. Symantec’s PKI unit faced a browser distrust campaign and was sold to DigiCert. Entrust faced a Chrome distrust decision in 2024. Each case ended with a brand either shrinking, selling or leaving.
The eMudhra case differs in one respect. It chose to leave before a formal, prolonged distrust process dragged out for months. Browsers had already blocked the eight intermediates in days, and the company chose a voluntary exit within five days of discovery. That is faster than most earlier stories, and it spares the web a messy multi-year transition for certificates eMudhra says it never issued to end users.
The earlier cases also involved mis-issuance or concealed practices. This one involves a generation flaw that the company disclosed, which regulators and browsers may treat more mildly than deliberate misconduct. The company’s emphasis on prompt revocation and public disclosure follows from that distinction.
Competitive Picture: Who Gains From eMudhra’s Exit
Customers who must replace eMudhra certificates have an easy path to larger issuers and to free automated CAs such as Let’s Encrypt. The company itself said replacements will come through partners at no charge, which lowers the friction of switching but also hands the relationships to whoever those partners choose.
Free issuers gain the most, because the economic argument eMudhra cited in leaving is the same argument that favors them. Paid CAs that survive will need to sell something beyond the certificate itself, such as validation services, management platforms or compliance tooling. Large commercial CAs also pick up reputational advantage whenever a small rival stumbles on basic key hygiene.
Inside eMudhra, the gain goes to the enterprise side. Its emCA and CertiNext PKI platforms, the emSigner signature suite and the SecurePass and emAS identity products now carry the company’s pitch without the TLS distraction. Whether customers read the exit as a clean break or as a warning sign will play out in the next few quarterly reports.
What Site Owners and Security Teams Should Do Now
Start by finding out whether any of your endpoints chain to an eMudhra intermediate. A quick command shows the issuer of the certificate a server presents.
openssl s_client -connect example.com:443 -servername example.com </dev/null 2>/dev/null | openssl x509 -noout -issuer -subject -datesIf the issuer line names eMudhra or emSign, plan a replacement now. Do not wait for a browser warning to reach your customers. Business Today advised users to keep browsers and operating systems updated and to avoid bypassing certificate warnings, which applies equally to staff who might click through an interstitial on an internal tool.
| Audience | Action | Reason |
|---|---|---|
| Site owners | Check the issuer on every public endpoint and replace eMudhra-issued certificates | Browsers block the affected chains and users may see warnings |
| Security teams | Inventory every CA your organization trusts or depends on | Small-CA risk is invisible until an incident |
| IT administrators | Review private trust stores for manually added eMudhra roots | Browser blocks do not always reach custom stores |
| Developers | Pin to automation that can rotate certificates quickly | Fast replacement shrinks the outage window |
| Everyone | Never click through certificate warnings | A forged certificate looks valid only if the warning is ignored |
Hardening logins also limits the damage from a forged certificate. A phishing-resistant method such as passkeys ties authentication to the real site, which our guide to WebAuthn passkeys setup in 13 steps walks through. A forged certificate can still impersonate a page, but it cannot easily hand over a passkey credential.
Lessons for Key Management and Secrets Hygiene
The core failure here was a generation step that produced two key sets and published the wrong one. That kind of defect passes through human reviewers because the ceremony looks correct when you watch it. The fix is verification of the output, not only observation of the process. Anyone running a key ceremony should test the published public key against the intended private key before release, and should ask an outside party to attempt basic recovery.
Teams outside the CA world face a cousin of the same problem. Secrets scanners find keys that were committed, copied or generated badly, which we compared in TruffleHog vs Gitleaks vs GitGuardian. Weak entropy and forgotten key copies do not need a nation-state to cause harm. They need only one researcher with patience.
The AI angle deserves a measured note. eMudhra said the researcher possibly used AI-assisted techniques. If that is correct, it fits the pattern in our coverage of the AI-found PHP2Shell flaw, where automated analysis surfaced a defect that humans had missed. Defenders should assume the same tools are available to attackers and should audit their old keys accordingly. More security coverage lives in our cybersecurity section.
Five Predictions for the Certificate Market
These are our analysis, not reported facts.
- The root-cause report will drive new rules. eMudhra owes the browser programs a full report, and we expect root programs to cite it when they tighten expectations around key-generation ceremonies.
- More small CAs will review their TLS lines. The same free-certificate economics that pushed eMudhra out apply to other low-volume issuers.
- Output verification becomes standard. Auditors will likely ask CAs to prove that published keys match intended keys, not only that a ceremony followed a script.
- The G1 RSA roots wind down gradually. Given the company’s plan to keep serving customers until the transition ends, expect a managed sunset rather than a sudden cutoff.
- The enterprise PKI business absorbs the attention. eMudhra will steer investor and customer conversations toward emCA, CertiNext and its signature products, and its next results will show whether that message holds.
The Takeaway
eMudhra’s exit closes a small business line but opens a large question about how many public CAs hold keys that no one has tested. The company revoked fast, disclosed the cause and kept its India signature and enterprise lines intact. It also left a public trust gap that lasted from April 30, 2025 to October 17, 2026. For buyers and defenders, the lesson is to verify what you trust instead of assuming a clean audit means clean keys.
FAQ
What did eMudhra announce on October 22, 2026?
The company’s board decided to voluntarily withdraw from the global SSL/TLS certificate business. The decision follows an incident involving eight intermediate certificate authorities with weak private keys.
How weak were the compromised keys?
Reporting that cites the security researcher’s finding put the effective key space at 3 to 8 bits. TNW reported that one key was the number 4.
Are eMudhra’s Indian DSC and eSign services affected?
No, according to both the company and India’s IT ministry. They say those services run on infrastructure separate from the global TLS business.
Did attackers use the weak keys?
As of October 21, Business Today reported that public reports had not established widespread attacks using the keys. It cautioned that this does not prove the keys went unused.
Which browsers blocked the certificates?
Google Chrome, Mozilla Firefox, Apple Safari and Microsoft Edge moved to block the affected certificates by October 20, 2026. Business Today added that Google planned to remove the emSign ECC Root CA G3 certificate from its trust store.
Do I need to replace my certificate?
If your site’s certificate chains to an eMudhra intermediate, yes. TNW reported the company will contact affected customers and replace certificates free of charge through partners, but you should check your own chain first.
How much of eMudhra’s revenue came from global TLS?
Co-founder Kaushik Srinivasan said the affected global TLS business accounts for around 1% of company revenue.
