---
title: "4 real? Tracking exploitation and patching of eMudhra’s weak keys"
description: "eMudhra’s eight shockingly weak intermediate private keys, including the number 4, could be recovered instantly from public certificates, allowing anyone to forge certificates for any domain. Cloudflare patched high-impact systems within hours on October 19, 2026, using Pingora to reject the vulnerable keys and AI-assisted code analysis to identify all affected systems. By October 21, logging detected about 22,000 handshakes with the weak keys, with two-thirds being test site fetches and most of the rest appearing to be servers using the weak intermediate themselves. About 160 handshakes involved forged certificates naming other organizations’ domains, including consumer IoT domains, with one forged certificate dated less than an hour after the weakness became public. Cloudflare’s challenge page probes show that while modern browsers are mostly patched, bots, old browsers, and embedded browsers like Android WebView still accept the compromised chain, with over half of probes on large networks still vulnerable."
---

# 4 real? Tracking exploitation and patching of eMudhra’s weak keys

[Cloudflare](https://yomu.fyi/company/cloudflare) · Bas Westerbaan · Oct 30, 2026

**Type:** Incident / postmortem

## Summary

eMudhra’s eight shockingly weak intermediate private keys, including the number 4, could be recovered instantly from public certificates, allowing anyone to forge certificates for any domain. Cloudflare patched high-impact systems within hours on October 19, 2026, using Pingora to reject the vulnerable keys and AI-assisted code analysis to identify all affected systems. By October 21, logging detected about 22,000 handshakes with the weak keys, with two-thirds being test site fetches and most of the rest appearing to be servers using the weak intermediate themselves. About 160 handshakes involved forged certificates naming other organizations’ domains, including consumer IoT domains, with one forged certificate dated less than an hour after the weakness became public. Cloudflare’s challenge page probes show that while modern browsers are mostly patched, bots, old browsers, and embedded browsers like Android WebView still accept the compromised chain, with over half of probes on large networks still vulnerable.

## Context

On October 19, 2026, eMudhra’s eight shockingly weak intermediate private keys (including the number 4) were disclosed. These keys could be recovered instantly from public certificates, allowing anyone to forge certificates for any domain. eMudhra announced they are exiting the public CA business and claimed a mistake in a key generation script. Cloudflare responded by patching its systems and tracking exploitation and patching progress across the Internet.

## Approach / What changed

Cloudflare patched high-impact systems within hours on October 19, 2026, by updating Pingora to reject certificates signed by eMudhra’s weak keys. They used AI-assisted source code analysis to identify all systems trusting those keys within four hours, assigning tickets for each. To detect exploitation, they added logging to Pingora to record any handshake presenting a weak-key certificate. To measure visitor vulnerability, they deployed challenge page probes that send two connections—one with an eMudhra-signed certificate and one with a regular certificate—and record whether the probes succeed.

## Takeaways

- eMudhra’s weak intermediate keys (e.g., the number 4) could be recovered instantly from public certificates, enabling anyone to forge certificates for any domain without special access.
- Cloudflare patched high-impact systems within hours using Pingora and AI-assisted code analysis, and added logging to detect handshakes with the weak keys.
- As of late October 2026, over half of probes on large networks still accept the compromised chain, with bots, old browsers, and embedded browsers like Android WebView lagging in patching.

## FAQ

### How did Cloudflare detect exploitation of the weak keys?

Cloudflare added logging to Pingora to track any handshake presenting a certificate signed by eMudhra's weak keys. By October 21, they had seen about 22,000 such handshakes, with most being test site fetches or servers using the weak intermediate themselves.

### What evidence of forged certificates was found?

About 160 handshakes involved certificates with SANs naming other organizations' domains, including consumer IoT domains. One forged certificate was dated less than an hour after the weakness became public, but these appeared to be server default certificates rather than interception attempts.

### How vulnerable are visitors still?

Cloudflare's challenge page probes show that modern browsers are mostly patched, but bots, old browsers, and embedded browsers like Android WebView still accept the compromised chain. Over half of probes on large networks remain vulnerable.

**Tags:** [Certificate Authority](https://yomu.fyi/topic/certificate-authority), [Cryptography](https://yomu.fyi/topic/cryptography), [Incident Response](https://yomu.fyi/topic/incident-response), [Security](https://yomu.fyi/topic/security), [Vulnerabilities](https://yomu.fyi/topic/vulnerabilities)

- Source: [Cloudflare](https://blog.cloudflare.com/emudhra-patching)
- Source URL: https://blog.cloudflare.com/emudhra-patching
- Ingested by Yomu: 2026-10-30T18:00:10.131Z

[Read original post](https://blog.cloudflare.com/emudhra-patching)
