A company that vouches for websites had secret keys so weak that 8 of them were cracked

Eight private keys belonging to eMudhra, an Indian certificate authority, were compromised. These keys acted like master stamps for signing website certificates. Anyone controlling one could potentially create an authentic-looking certificate for another website. That could support a man-in-the-middle attack, where an attacker intercepts and changes traffic.

The certificates mattered because browsers trust certificate authorities to identify real websites. Researchers recovered the eight keys from public certificates in under a second. They then used the keys to digitally sign a warning message. Because the certificates could no longer be trusted, browser makers treated them as an emergency threat.

Mozilla blocked them roughly three hours after receiving the report on October 17. Chrome acted the same day, while Apple followed on October 19 and Microsoft on October 20. eMudhra also revoked the certificates. The article says no attacks were reported, but outdated software remains exposed.

A certificate authority, or CA, is a company that vouches for websites. It issues digital certificates that connect a website’s identity with cryptographic information used to secure the connection. Browsers trust selected certificate authorities, so a certificate signed by one can help prove that a site is genuine.

The CA signs each certificate with a private key. That signature works like a master stamp. When a browser receives the certificate, it checks the signature using the CA’s public information. If the signature is valid and the certificate is acceptable, the browser can treat the website as trusted rather than an unknown site.

This system makes protecting the CA’s private keys essential. In the eMudhra incident, attackers could potentially use compromised keys to forge certificates for other websites. Browser makers therefore blocked the affected certificates, while eMudhra revoked them. The article identifies eMudhra as a CA that had issued more than 60 million certificates.

eMudhra had issued more than 60 million certificates, according to The Register. That figure shows the company’s broad role in the system that helps browsers identify websites. The danger was not limited to the eight individual certificates tied to the compromised keys.

A certificate authority uses private keys to sign certificates. The private key is the authority’s master stamp. If an attacker obtains one, the attacker may be able to create a new certificate for a different website and make it appear authentic. The attacker could then try to impersonate that site to users or software that trusts the CA.

Browser makers blocked the affected certificates, and eMudhra revoked them. Mozilla, Chrome, Apple, and Microsoft moved quickly, while fixes also targeted some programming tools. However, the article says many programs do not check revocation status. That means the wider risk extends beyond browsers, especially to older or unpatched software.

A forged certificate can make an attacker appear to be a trusted website. That creates the possibility of a man-in-the-middle attack. The attacker intercepts a connection, presents the forged certificate, and may then read or alter information moving between the user and the intended service.

The article gives a crypto example. Exchange bots, trading scripts, and wallet backends often use Python, Node, or Go. A forged certificate for an exchange’s API could, in theory, let an attacker on the same network inspect or change a bot’s traffic. The article reports that tests showed several tools accepted a forged certificate for Stripe’s API.

No crypto attacks were reported. Browser makers blocked the affected eMudhra certificates, and eMudhra revoked them. Still, some software does not check whether certificates have been revoked. The article says the main concern is generic, not crypto-specific, and especially affects users running older or unpatched software.

Researchers said eMudhra used tiny integers as private keys instead of strong, random cryptographic values. Examples reported in the article include 4, 56, and 237. Such numbers are easy to test because the possible choices are extremely limited. Scott Helme said he recovered all eight keys from public certificates in under a second.

A private key is supposed to be secret and unpredictable. It should be generated as a very large random number, making guesses impractical. The article describes a proper key as a huge random number and mentions strong 384-bit random numbers. Guessing one should require far more attempts than an attacker can realistically perform.

The exact cause remains unclear, but a Mozilla bug-ticket reading says eMudhra blamed a bug in its key-setup script. The keys had reportedly been exposed since April 2025. Browser makers blocked the certificates, and software fixes were released for Go, Python’s certifi package, and Rust’s webpki-roots.

Browsers usually receive updates that block certificates or certificate authorities known to be unsafe. That lets them reject a revoked certificate even if the certificate still appears correctly signed. In this incident, Mozilla, Chrome, Apple, and Microsoft pushed blocks quickly after the eight eMudhra keys were reported.

Many other programs handle certificates differently. The article says tools such as curl, Python, Node, Go, and Java may not check whether a certificate has been revoked. If they only verify the signature and other basic details, they could continue accepting a forged certificate made with a compromised key. Helme said tests showed several tools accepted a forged certificate for Stripe’s API.

The risk is being reduced through software fixes. Updates were available for Go, Python’s certifi package, and Rust’s webpki-roots, while Node.js was still pending when checked. The incident shows why revocation alone may not protect outdated or incomplete software.

Digital certificates help a browser decide whether a website is genuine. A certificate identifies the site and contains information used to establish a protected connection. A certificate authority signs that information with its private key. The browser checks the signature using the authority’s corresponding public information and verifies that the certificate is trusted.

The private key is the critical secret. It acts as the CA’s master stamp, proving that the authority approved the certificate. If an attacker obtains or cracks it, the attacker can potentially sign a certificate for a different website. A victim’s browser may then accept the impostor as trusted, allowing a man-in-the-middle attack that reads or alters traffic.

That is why browser makers blocked eMudhra’s certificates after eight keys were compromised. Mozilla warned that network interceptors could use fraudulent certificates to impersonate trusted sites. No attacks were reported, but older or unpatched software may remain vulnerable when it does not check revocation.