eMudhra security breach: What it means for smartphone, internet users

eMudhra is an Indian cybersecurity and digital trust company. It is a Certificate Authority, or CA. CAs issue digital certificates that work like ID cards for websites. When you visit a site, your browser uses the certificate to check whether the site is genuine rather than an impostor. Major browsers, including Chrome, Firefox, and Safari, keep lists of trusted CAs, and eMudhra was included on those lists.

The company sells certificates under the emSign brand through companies in India, the United States, and the Netherlands. Its certificates can also be used through intermediate certificates. These are like authorised retail partners. Each intermediate certificate has a secret key, similar to an official stamp, allowing its holder to issue certificates that browsers recognize as valid.

That trust makes a CA’s security crucial. If an intermediate key is weak or misused, an attacker could potentially create convincing certificates for unrelated websites. The incident involved eight weak intermediate certificates, not eMudhra’s main root keys or all its other certificates.

The problem was not that the certificates had been stolen. Their secret keys were generated with far too little randomness, making them easy to calculate from public certificate information. A proper key should have an enormous number of possible values, roughly 1 followed by 115 zeros. Instead, the eight keys were tiny numbers.

The keys were 4, 56, 66, 115, 155, 156, 230, and 237. Six certificates were intended for websites, while two were intended for signing software. Researchers compared the weakness to a padlock with only 256 possible combinations. Trying every combination would take almost no time, and they recovered all eight keys in less than a second.

According to eMudhra, a flaw in its April 2025 certificate-creation process produced a weak second set of keys alongside the intended strong keys. The weak keys were published to browser trust lists. eMudhra said the issue did not affect its main root keys or other intermediate certificates.

The incident affected eight intermediate certificates issued by eMudhra. Six were intended for websites, and two were intended for signing software. Intermediate certificates matter because they can issue additional certificates that browsers accept as genuine. Their secret keys therefore needed strong, unpredictable randomness.

Instead, the keys were tiny values: 4, 56, 66, 115, 155, 156, 230, and 237. The article explains the weakness with a padlock example. A secure lock has too many combinations to test. These keys were like a lock with only 256 possible combinations. Researchers tested the possibilities and recovered all eight secret keys in less than a second.

The keys were not stolen from eMudhra’s systems. Google’s security teams said anyone could work them out from the public certificates. eMudhra attributed the problem to a flaw in its April 2025 process, which created and published a weak second set of keys alongside stronger intended keys.

Possessing one of the weak keys could let an attacker issue a certificate for any website that a browser would accept. Certificates normally help browsers confirm that a site is genuine. A forged certificate could defeat that check and make an impostor site look legitimate.

For example, an attacker could create a certificate for a bank or shopping website. A user might see what appeared to be the real site and have no browser warning. The attacker could potentially read or alter sensitive information moving between the user and the website. The danger came from the browser trusting the certificate, not from a direct theft of eMudhra’s keys.

The certificates were blocked after a researcher reported the problem on October 17 and demonstrated it by signing a message with each key. Chrome and Firefox blocked them within hours. Apple blocked them on October 19, Microsoft on October 20, and Android received a similar block through Google Play Services. No evidence of misuse has been reported.

A researcher reported the weakness to browser companies on October 17. To demonstrate the problem, the researcher signed a message with each of the eight weak keys. Chrome and Firefox blocked the certificates within hours, preventing them from being trusted by those browsers.

Apple blocked the certificates on October 19, and Microsoft followed on October 20. Android phones received a similar block through Google Play Services on October 19. eMudhra revoked all eight intermediate certificates. Cloudflare and other software providers also released fixes. These actions were designed to remove the weak certificates from systems that could otherwise trust them.

Mozilla later removed one of eMudhra’s main roots, emSign ECC Root CA - G3, from its trusted list on October 20. Chrome planned to remove the same root in its next trusted-list update. The company said there was no evidence that the weak certificates had been used in an attack, though misuse could not be known with certainty.

Ordinary users could have faced convincing fake websites if the weak certificates had remained trusted. A fake bank or shopping site might have appeared legitimate, and an attacker could potentially read or alter information exchanged with it. However, the article reports no evidence that the keys were used in a cyberattack.

Protection came mainly through trust-list changes and software updates. Chrome, Firefox, Apple, Microsoft, and Android blocked the certificates. Android phones received the change through Google Play Services. Cloudflare and other software providers also released fixes. Chrome said no website certificates issued through the six website certificates appeared in the public logs it requires before blocking.

The article does not require users to take a special manual step. Keeping browsers, phones, and other software updated helps ensure these fixes arrive. eMudhra said only one of the eight certificates had been put to use, and none had issued a certificate to an individual website. Its separate Indian digital-signature and eSign systems were not connected.