eMudhra certificate keys were guessable: one was the number 4

The certificates in question were intermediates, a middle layer that signs the certificates websites actually show you. Eight of them, created in April 2025, used a type of key called P-384. A healthy P-384 key is packed with randomness. These held tiny single-byte values, ranging from 4 up to 237.

eMudhra told Mozilla that a script used during the key creation process contained an error. It produced a second set of weak keys alongside the proper ones, and because the labels looked alike, the weak set was picked for signing and published to browser trust stores. Some of the certificates were also cross-signed by another authority, Sectigo, creating duplicate copies with the same weak public key.

The affected certificates covered all three main grades of website certificate (domain validated, organization validated and extended validation) plus two used for signing software code.

A researcher known only as Wayne spotted the problem on October 17 while scanning public certificate records. To prove it, Wayne signed the message We have a problem here with each of the eight keys and sent it to the browser root programs.

The response was quick:

• Chrome got the report at 18:05 UTC on October 17 and blocked the six website certificates by 19:45 UTC, using a list Chrome downloads in the background.
• Firefox pushed its own block the same evening through a system that needs no update or restart. Mozilla also recovered the keys itself within two hours and later shipped a Firefox update for setups that skip those background lists.
• Apple added protection on October 19, and Microsoft followed on October 20.
• Android phones received an equivalent block through Google Play services on October 19.

eMudhra has revoked all eight certificates and stopped issuing new ones under the affected root. Mozilla removed that root from Firefox’s list on October 20.

There’s no evidence of it. Google’s Chrome team said no website certificate chaining to the six affected intermediates had been logged in Certificate Transparency, the public record browsers check, before its block went in. That means Chrome and any browser that requires such logging would not have trusted a forged one by default.

That isn’t a complete all-clear. The weak keys existed from April 2025, and nobody can prove what happened in that time outside the browsers’ view. eMudhra says most of the intermediates never went into production use and that no customer website certificate was issued with a weak key. A company executive, Kaushik Srinivasan, said its digital signature and eSign services in India are unaffected and that replacing certificates will take a few days. Chrome added that it checked every other authority in its store and found no other case of this failure.

If you browse with Chrome, Safari, Firefox or Edge on an up-to-date device, you’re already covered. These blocks arrived silently in the background. Still, it’s a good moment to do three quick things:

1. Install pending updates on your phone, computer and browser. On iPhone, look in Settings, General, Software Update; on Android, check Settings for system and Google Play updates.
2. Never click through a certificate warning, especially on banking or shopping sites. That warning is the alarm this whole system is built around.
3. Be wary of login links in texts and emails. Type your bank’s address yourself instead.

You don’t need to delete certificates or change advanced security settings. Doing that by hand is more likely to cause problems than fix them.

The weak spot now is software that keeps its own list of trusted authorities and doesn’t check revocation. That includes many apps built with the Go programming language and anything relying on the certifi bundle used widely in Python. These keep trusting a certificate until their own code or bundle is updated.

• Go has shipped security releases that reject any chain containing one of the eight keys, but programs only pick this up when rebuilt.
• certifi, the webpki-roots library and Homebrew’s certificate package have dropped the affected eMudhra root.
• A Mozilla engineer warned that the curl tool built into macOS may keep trusting the certificates, because its bundle doesn’t check revocation.

If you run servers, write code or manage company laptops, update those components this week. Mozilla’s engineer has published a tracking page listing affected software and fixes, which is the best checklist to follow.