eMudhra to Exit Global Website Security Certificate Business After Key-Generation Flaw

eMudhra Limited has decided to withdraw from the global website authentication certificate business after a serious cryptographic key-generation flaw affected eight intermediate certificate authorities. The Bengaluru-based company announced the decision on October 22, 2026, following an investigation that found private keys associated with the affected certificates could be recovered. The incident prompted major browser and certificate-trust programmes to block the compromised certificates.

The decision concerns eMudhra’s international SSL/TLS certificate operations, which help websites establish trusted, encrypted connections with users. Its Indian digital signature certificate and eSign businesses are separate and remain operational, according to the company. Although the affected global business contributes approximately 1% of revenue, the incident creates potential reputational risks and puts renewed attention on the controls used to protect the internet’s certificate infrastructure.

Key Takeaways

• Business exit: eMudhra’s board decided on October 22, 2026, to exit the global website-security certificate business.
• Eight affected authorities: Private keys associated with eight intermediate certificate authorities were found to be weak and recoverable.
• Key-generation flaw: A problem during an April 2025 key-generation ceremony resulted in weak keys being used in the affected certificates.
• Browser response: Google and Mozilla blocked the affected website-security certificates; browser and trust-store operators have taken additional protective measures.
• Limited direct revenue exposure: The global TLS business accounts for around 1% of eMudhra’s revenue, according to the company.
• Indian services continue: Domestic digital signature certificates and eSign services remain operational on separate infrastructure.
• Investigation ongoing: The company is reviewing the root cause and its key-generation and operational controls.

1. Why Is eMudhra Exiting the Global Certificate Business?

eMudhra’s decision follows a security incident involving certificates used to establish trust in websites and other digital services. These certificates sit within the public key infrastructure (PKI), a system that allows browsers and applications to verify digital identities through trusted certificate authorities.

The company said the affected certificates originated from a key-generation ceremony conducted on April 30, 2025. A flaw in the process created a second set of weak keys alongside the intended strong keys. The weak keys were subsequently used in eight intermediate certificate authorities.

An independent security researcher identified the problem and reported it to major browser root programmes in October 2026. Mozilla independently recovered the affected private keys, confirming that the flaw was exploitable.

Following the discovery, eMudhra revoked the affected certificates and worked with browser vendors and other trust-store operators. The company’s board subsequently decided to exit the global website-security certificate business.

The decision is significant because certificate authorities depend on the confidence of browsers, operating systems, software vendors and website operators. Once that confidence is undermined, continued participation in the global trust ecosystem can become commercially and operationally difficult.

2. What Went Wrong With the Key-Generation Process?

Digital certificates rely on cryptographic private keys that must be generated using sufficiently unpredictable values. If a private key is predictable or too easy to recover, an attacker may be able to impersonate the certificate authority that owns it.

According to eMudhra’s disclosure, the incident originated during the April 2025 key-generation ceremony. A flaw in a key wrap-and-unwrap process created weak keys alongside the intended strong keys. The company is investigating how the error occurred and why the weak keys were used.

India’s Computer Emergency Response Team (CERT-In) said the affected P-384 elliptic-curve private keys had values smaller than 256, making them recoverable from their corresponding public keys. This was a failure in the generation process, not evidence that the underlying P-384 cryptographic algorithm itself was broken.

The distinction matters. Modern cryptographic algorithms can be secure when implemented correctly, but implementation errors and failures in key management can undermine their protection.

The incident also illustrates why a security process must do more than use specialised hardware or pass periodic audits. Key generation, verification, approval, certificate issuance and revocation must all operate correctly, with controls capable of detecting mistakes before certificates enter trusted systems.

3. How Could the Flaw Have Threatened Website Security?

SSL/TLS certificates help browsers verify that a website is associated with the identity represented by its certificate. They also enable encrypted connections that protect information exchanged between users and websites.

A compromised intermediate certificate authority can create a serious risk because its private key may allow an attacker to issue fraudulent certificates for domains the attacker does not control. If those certificates were accepted by a user’s browser or application, an attacker in a suitable position could attempt to impersonate a legitimate website or intercept communications.

The affected eMudhra certificates included six intended for TLS website security and two intended for code signing. Code-signing certificates are used to establish the publisher and integrity of software. If a code-signing private key is compromised, fraudulent software could potentially be made to appear signed by a trusted publisher.

However, the existence of a vulnerable key does not by itself establish that it was used in a successful attack. eMudhra said the affected intermediate authorities had not issued certificates to individual websites or end users. Google also reported that no TLS certificates chaining to the six affected intermediates had appeared in the relevant public Certificate Transparency logs before Chrome blocked them.

These findings are important risk-mitigation evidence, but they do not remove the need to investigate the key-generation failure and address any systems that might still trust the affected certificates.

4. Google and Mozilla Move to Block the Certificates

Browser security teams acted after receiving reports of the compromised keys.

Google said it blocked the affected TLS intermediate public keys in Chrome through a Certificate Revocation List Set (CRLSet) update on October 17, 2026. This protection was delivered without requiring users to restart their browsers or install a conventional browser update.

Mozilla also blocked the affected certificates through Firefox’s OneCRL mechanism. It subsequently released security updates for supported Firefox versions and began updating its Network Security Services (NSS) certificate store.

Google announced that it would remove the emSign ECC Root CA – G3 certificate, which signed the affected intermediates, from the Chrome Root Store. That removal was expected to reach devices relying on the Chrome Root Store on October 27, 2026, Pacific Daylight Time.

Removing a root certificate can have consequences beyond the compromised certificates themselves: legitimate certificates that chain to that root may stop being trusted by affected software. Google therefore advised website operators using the impacted trust chain to obtain replacement TLS certificates from another trusted certificate authority.

The response demonstrates how browser vendors can distribute protections across large user populations, but it also highlights the work organisations may need to do to replace certificates and update systems that use separate or outdated trust stores.

5. What Does the Exit Mean for eMudhra’s Revenue?

eMudhra said its global TLS certificate business contributes approximately 1% of total company revenue. That suggests the direct revenue exposure is limited relative to its broader operations.

However, the financial consequences cannot be assessed from revenue contribution alone. The company may face transition costs, customer migration requirements, certificate replacement work and potential reputational damage. It has acknowledged that the reputational impact cannot yet be quantified.

The company’s Indian digital signature certificate and eSign services are not affected by the incident, according to its disclosures. These services run on separate infrastructure and use distinct cryptographic keys under a different operational and regulatory framework.

That separation is central to understanding the scope of the incident. The decision to exit the international website-security certificate business does not mean eMudhra has announced a shutdown of its domestic digital signature or eSign operations.

Investors will need to monitor the company’s subsequent disclosures for details about the exit, any associated costs, the handling of affected customers and the results of its investigation.

6. What Should Website Operators and Businesses Do?

Organisations using certificates associated with the affected eMudhra trust chain should follow the relevant browser-vendor and CERT-In guidance. The immediate priority is to determine whether their websites, applications or infrastructure depend on certificates that may become untrusted.

Businesses should review certificate chains, obtain replacement certificates where necessary and test their services after migration. IT teams should also check whether applications use their own certificate stores instead of relying on the operating system or browser’s standard trust store.

Security teams should apply relevant software and trust-store updates, review certificate-management processes and confirm that certificate validation remains enabled. Disabling certificate verification to bypass errors would remove an important security protection rather than resolve the underlying problem.

The incident also provides a broader lesson for organisations managing cryptographic infrastructure: key generation and lifecycle controls require rigorous testing, independent verification and documented approval procedures. Hardware security modules can help protect keys, but they cannot compensate for every flaw in the surrounding software and operational process.

The Bigger Picture

eMudhra’s exit highlights the importance of trust in the global digital certificate ecosystem. Certificate authorities operate as part of a shared security framework: browsers, operating systems, developers and website owners all depend on their ability to generate and manage cryptographic keys correctly. A failure at one point can require coordinated action across many independent organisations.

The incident also demonstrates why the security of cryptographic systems depends on implementation as well as algorithm design. Weak key generation can undermine otherwise robust encryption standards, while rapid revocation and browser updates can help limit the consequences. For eMudhra, the immediate priorities are completing the exit, assisting affected customers and establishing the precise cause of the failure.

FAQs

1. Why is eMudhra exiting the global website-security certificate business?

The company’s board decided to exit after a key-generation flaw affected eight intermediate certificate authorities. Their private keys were found to be recoverable, prompting browser security programmes to block the affected certificates.

2. Were eMudhra’s Indian digital signature and eSign services affected?

No, according to eMudhra and CERT-In. The domestic DSC and eSign businesses operate on separate infrastructure and continue to function normally.

3. How many certificate authorities were affected?

Eight intermediate certificate authorities were affected: six associated with TLS website security and two intended for code signing.

4. Does the incident mean the P-384 cryptographic algorithm is broken?

No. CERT-In attributed the weakness to the key-generation process. The affected private-key values were unusually small and could be recovered, rather than the underlying P-384 algorithm being shown to be broken.

5. What should businesses using affected certificates do?

Website operators and IT teams should identify affected certificate chains, follow browser-vendor and CERT-In guidance, replace certificates where required and update relevant software and trust stores. They should not disable certificate verification to work around errors.

Looking Ahead

The next steps will centre on eMudhra’s withdrawal from the global TLS certificate business, the migration of potentially affected customers and the completion of its root-cause investigation. Browser vendors may also continue reviewing the trust status of other eMudhra certificates, while organisations using affected trust chains will need to complete any required replacements before further trust-store changes take effect.

For the wider industry, the incident reinforces the need for strong cryptographic key-generation controls, independent verification and rapid incident response. Although eMudhra has said the affected business is small and its Indian DSC and eSign services remain unaffected, the longer-term impact will depend on the investigation’s findings, the effectiveness of customer migration and the confidence that businesses and browser vendors place in the company’s remaining services.