← Back to Tech · Phones & Mobile
a glowing golden padlock made of light hovering over a dark world map of network lines, with one link of its chain cracked and glowing red, security engineers’ monitors blurred in the background, cool blue and amber tones, no logos, no text

The padlock had a weak link: eight eMudhra certificates could have faked any website, and browsers moved fast to block them

The little padlock in your browser depends on certificate authorities keeping their keys secret. Over the weekend, a security researcher showed that eight intermediate certificate authorities run by India-based eMudhra had private keys so weak they could be recovered, which in theory let anyone forge a trusted HTTPS certificate for any site (Google, Ars Technica).

What’s already fixed

  • Chrome blocked the eight certificates on Oct 17, with no browser update or restart needed. Android got the same block through Google Play Services on Monday; restarting your phone grabs it right away (Google).
  • Firefox blocked them the same day, and Mozilla shipped Firefox 158.0.1 for users with custom settings (eMudhra, citing Mozilla).
  • No misuse found so far. Google says no certificates from these CAs showed up in public Certificate Transparency logs before the block. eMudhra says none of the eight ever issued a certificate and its systems weren’t breached.
  • Oct 27: Chrome removes the eMudhra ECC root behind them. Websites with certificates under that root need new ones now.

Why experts still call it big

Browsers update themselves. Plenty of other things don’t. Cryptography engineer Filippo Valsorda told Ars the cleanup could be “bigger than Heartbleed,” with a long tail of IoT devices, Docker containers, forgotten Linux machines and tools that bundle their own certificate lists. Ars says the most immediate risk is to VPN users on networks someone could intercept. Exploiting it takes an active man-in-the-middle attack, though, and Signal, WhatsApp and WireGuard don’t rely on TLS for privacy.

Update, Oct 21 evening: India steps in

India’s cybersecurity agency CERT-In issued an advisory on Oct 21 confirming the eight keys were generated with too little randomness, and told organizations to update browsers, operating systems and certificate lists and replace any affected certificates (India Today, CNBC-TV18).

India’s IT ministry (MeitY) set up a special team to investigate. Officials say eMudhra’s Indian digital-signature and eSign services are unaffected; the problem sits in its global website-certificate business. eMudhra told stock exchanges that business is about 1% of revenue, and its shares fell 20% on Wednesday (ThePrint).

Koffee take: update your browser, restart your phone, and install pending Linux and router updates this week. One weak link can shake the whole web, and a fix only counts once it reaches your devices.

Filed Oct 21, 2026 ~9:00 AM CT — Morning pass. Updated Oct 21, 2026 ~8:30 PM CT — Evening pass. Sources: Google Chrome and Android Security Teams — Protecting users from compromised eMudhra intermediate CA certificates (Oct 20, 2026) · Ars Technica (Oct 20, 2026) · eMudhra statement (updated Oct 21, 2026) · India Today — CERT-In advisory (Oct 21, 2026) · CNBC-TV18 (Oct 21, 2026) · ThePrint — MeitY probe (Oct 21, 2026).