---
title: "8 eMudhra certificates are compromised. Here's what you need to know"
description: "On October 19, 2026, Cloudflare learned that private keys for eight eMudhra intermediate certificates were compromised due to weak keys, allowing attackers to forge certificates for any domain and intercept or modify traffic. Cloudflare immediately patched critical services, updated shared trust stores and base images, released updates for Cloudflare One Clients and Cloudflare Tunnel, and deployed mitigations across CDN, Developer, and Zero Trust products. The security review found no active exploitation on Cloudflare services, but customers using mutual TLS or custom origin certificates must update trust stores and server configurations, and Cloudflare is updating Automatic SSL/TLS to notify affected users. Developers should update dependencies and verify the actual TLS verification path used by their applications, as a browser test does not prove a background service is protected. Browsers remediated quickly with CRLSets, and Cloudflare is working on further remediation while advocating for dynamic trust stores that can incorporate revocation information."
---

# 8 eMudhra certificates are compromised. Here's what you need to know

[Cloudflare](https://yomu.fyi/company/cloudflare) · Jeremy Hartman · Oct 20, 2026

**Type:** Incident / postmortem

## Summary

On October 19, 2026, Cloudflare learned that private keys for eight eMudhra intermediate certificates were compromised due to weak keys, allowing attackers to forge certificates for any domain and intercept or modify traffic. Cloudflare immediately patched critical services, updated shared trust stores and base images, released updates for Cloudflare One Clients and Cloudflare Tunnel, and deployed mitigations across CDN, Developer, and Zero Trust products. The security review found no active exploitation on Cloudflare services, but customers using mutual TLS or custom origin certificates must update trust stores and server configurations, and Cloudflare is updating Automatic SSL/TLS to notify affected users. Developers should update dependencies and verify the actual TLS verification path used by their applications, as a browser test does not prove a background service is protected. Browsers remediated quickly with CRLSets, and Cloudflare is working on further remediation while advocating for dynamic trust stores that can incorporate revocation information.

## Context

Cloudflare’s response to the compromise of eight eMudhra intermediate certificates with weak private keys, affecting certificate-based authentication across the Internet.

## Approach / What changed

Cloudflare prioritized patching services using public certificates for authentication, updated shared trust stores and base images, released client updates for Cloudflare One/WARP and Cloudflare Tunnel, and deployed server-side mitigations across CDN, Developer, and Zero Trust products. They also provided guidance for customers and developers to update their own configurations and dependencies.

## Takeaways

- The compromised eMudhra certificates had weak private keys, allowing attackers to forge certificates for any domain and impersonate servers.
- Cloudflare’s security review found no evidence of active exploitation on their services, but customers must update trust stores and origin server configurations.
- Developers should update dependencies and verify the actual TLS verification path used by their applications, as a browser test does not guarantee protection for background services.

## FAQ

### What should Cloudflare One/WARP users do?

Upgrade to the specified versions: Android v2.5.6, iOS v1.12.16, Windows Desktop 2026.8.2115.0, macOS 2026.8.2115.0, Linux 2026.8.2115.0 for Cloudflare One Client and 1.1.1.1 app.

### How can developers ensure their applications are protected?

Update dependencies, rebuild images, and verify the actual TLS verification path used by the application, not just a browser test. Look at the dependency tree for affected packages.

### Are browsers affected by this incident?

Browsers were able to remediate quickly using CRLSets, but non-browser applications may still be vulnerable if not updated.

**Tags:** [Certificate Authority](https://yomu.fyi/topic/certificate-authority), [Cryptography](https://yomu.fyi/topic/cryptography), [Security](https://yomu.fyi/topic/security), [TLS](https://yomu.fyi/topic/tls)

- Source: [Cloudflare](https://blog.cloudflare.com/emudhra-certificate-compromise)
- Source URL: https://blog.cloudflare.com/emudhra-certificate-compromise
- Ingested by Yomu: 2026-10-21T00:00:20.276Z

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