Pull to refresh
Logo
Weak eMudhra certificate keys trigger global TLS cleanup

Weak eMudhra certificate keys trigger global TLS cleanup

New Capabilities

Eight intermediate certificates had private keys recoverable in seconds, forcing browser makers to block them

Yesterday: Firefox releases emergency updates

Overview

Updated 1 hour ago

Eight digital certificates that vouch for website identities had private keys so weak that anyone could recover them by testing a few hundred numbers. The keys belonged to eMudhra, an Indian certificate authority, and could have let attackers forge credentials for any website on the internet.

Browser makers blocked the certificates within hours of the October 17 report. The cleanup extends far beyond browsers: Linux distributions, Docker containers, and internet-connected devices that trust the certificates may remain vulnerable for months.

Why it matters

If attackers exploited these keys, they could impersonate any website and read encrypted traffic on networks they control.

Questions about this story

Free account needed to ask — your question is kept and asked for you right after sign-up. Answers are public.

No questions yet — be the first to ask.

Key Indicators

8
Compromised certificates
Intermediate certificates with trivially recoverable private keys.
3-8 bits
Private key entropy
Normal P-384 keys contain about 384 bits of entropy.
90 minutes
Chrome response time
Time from report to CRLSet block on October 17.
3 hours
Firefox response time
Time from report to OneCRL block on October 17.

Voices

Curated perspectives — historical figures and your fellow readers.

Ever wondered what historical figures would say about today's headlines?

Sign up to generate historical perspectives on this story.

People Involved

Organizations Involved

Timeline

April 2025 October 2026

8 events Latest: Yesterday
Tap a bar to jump to that date
  1. Root removal scheduled

    Upcoming Mitigation

    Google plans to remove emSign ECC Root CA - G3 from the Chrome Root Store.

  2. Firefox releases emergency updates

    Latest Mitigation

    Firefox 158.0.1 and ESR updates ship to cover users whose custom settings blocked OneCRL.

  3. Sectigo revokes certificates

    Mitigation

    Sectigo revokes certificates chaining to the compromised intermediates.

  4. eMudhra revokes certificates

    Mitigation

    eMudhra revokes the eight compromised intermediate certificates.

  5. Compromise reported

    Disclosure

    Security researcher reports the weak keys to the Chrome Root Program, proving control by signing a message.

  6. Chrome blocks certificates

    Mitigation

    Chrome lands a CRLSet update blocking the affected intermediate certificates by key hash.

  7. Firefox blocks certificates

    Mitigation

    Mozilla completes OneCRL distribution blocking the affected certificates for all standard Firefox users.

  8. Weak keys generated

    Incident

    eMudhra generates eight intermediate certificates with private keys containing 3-8 bits of entropy.

Scenarios

1

No fraudulent certificates found in the wild

Likely Resolves by Jan 31, 2027

Discussed by: Chrome Root Program, Mozilla

Certificate transparency logs show no fraudulent certificates issued from the compromised intermediates before they were blocked. If this holds, the incident becomes a near-miss: the weak keys were discovered before they were exploited. The cleanup continues for months as Linux distributions and IoT devices update their trust stores.

2

Fraudulent certificates discovered

Unlikely Resolves by Jan 31, 2027

Discussed by: Security researchers

An attacker used one of the weak keys to issue a certificate for a high-value domain. The certificate could have been used in a man-in-the-middle attack against VPN users or other targets. Discovery would come from CT log monitoring or a security researcher's investigation.

3

Root removal breaks legitimate websites

Possible Resolves by Nov 30, 2026

Discussed by: Google, eMudhra

Google removes emSign ECC Root CA - G3 from the Chrome Root Store on October 27. Websites with certificates chaining to this root stop working in Chrome. eMudhra has committed to helping customers migrate, but some may not complete the transition in time.

Historical Context

3 moments from history that rhyme with this story — and how they unfolded.

July-September 2011

DigiNotar breach (2011)

In July 2011, attackers breached Dutch certificate authority DigiNotar and issued fraudulent certificates for Google, Yahoo, Mozilla, and Tor. The breach went undetected for over a month.

Then

Browser makers revoked trust in DigiNotar within days. The company filed for bankruptcy in September 2011.

Now

The incident led to stricter CA oversight and helped drive the development of certificate transparency.

Why this matters now

Shows the consequences of a compromised CA: browsers revoke trust, and the CA often collapses.

April 2014

Heartbleed bug (2014)

In April 2014, researchers disclosed Heartbleed, a bug in OpenSSL that let attackers read memory from servers. The bug affected an estimated 17% of secure web servers.

Then

Organizations worldwide rushed to patch and rotate keys. The bug was patched within days, but cleanup took months.

Now

Led to the creation of the Core Infrastructure Initiative and increased funding for OpenSSL.

Why this matters now

Filippo Valsorda compared the eMudhra cleanup to Heartbleed, noting the long tail of affected devices.

May 2012

Flame malware (2012)

In May 2012, researchers discovered the Flame malware, which used a forged Microsoft certificate to spread. The certificate was signed using a weak MD5 hash collision.

Then

Microsoft issued an emergency update to block the certificate.

Now

Demonstrated that even major software vendors can have weak cryptographic implementations.

Why this matters now

Shows how weak cryptographic material can be exploited to forge trusted credentials.

Sources

(8)