8 eMudhra certificates are compromised. Here's what you need to know
Web page · https://blog.cloudflare.com/emudhra-certificate-compromise
Following the discovery that eight eMudhra intermediate certificates use weak keys, Cloudflare is deploying mitigations and releasing client updates. We explain the impact, our response, and what customers and developers should do next.
First seen by Oriel on .
AI summary
Cloudflare reports compromised private keys for eight widely trusted eMudhra intermediate certificates, enabling server impersonation, and details deployed mitigations and required customer updates; its review found no active exploitation on Cloudflare services.
- Cloudflare learned of the compromise on October 19, 2026, around 17:00 UTC; the issue affects certificate authentication, not TLS encryption algorithms.
- Customers should install the listed platform-specific Cloudflare One/WARP updates and upgrade cloudflared to 2026.10.2, redeploying fixed container images where applicable.
- Customers must review custom mutual TLS trust stores, origin certificates, and container dependencies; HTTPS egress interception protects intercepted container connections through Cloudflare-managed certificate validation.
- Developers should update the actual certificate verifier and affected dependencies, rebuild images, and restart or redeploy as needed; updating an SDK alone may be insufficient.
- Validate each application's actual TLS verification path, since browser or curl checks may use different verifiers, and never disable certificate verification to suppress resulting errors.
#tls #webpki #cloudflare #certificate revocation
Generated by gpt-5.6-sol. Check the original for details.
Aliases
| Source | External ID | URL |
|---|---|---|
| Cloudflare Blog | 01M5DK5J81T0VC8YTBR2FKD8A3 | https://blog.cloudflare.com/emudhra-certificate-compromise/ Read discussion |