Authentication bypass via conflicting per-Ingress TLS options
Published Sep 4, 2026 · Updated Sep 4, 2026
Authentication bypass in Traefik Proxy 3.7.0 through 3.7.10 allows remote attackers to reach mTLS-protected routes without a client certificate. The Kubernetes Ingress NGINX provider includes each Ingress identity in generated TLS-option names, causing equivalent same-host policies to conflict and fall back to a default that requests no client certificate. Exploitation requires two HTTPS Ingress objects for one host with the same CA and client-authentication mode; successful requests can read protected content.
Summary
What happened
Authentication bypass in Traefik Proxy 3.7.0 through 3.7.10 allows remote attackers to reach mTLS-protected routes without a client certificate. The Kubernetes Ingress NGINX provider includes each Ingress identity in generated TLS-option names, causing equivalent same-host policies to conflict and fall back to a default that requests no client certificate. Exploitation requires two HTTPS Ingress objects for one host with the same CA and client-authentication mode; successful requests can read protected content.
The record
- CVE
- CVE-2026-85596
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- Traefik Labs
- Product
- Traefik Proxy
- Classifications
- CWE-287, CWE-295, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.7.0 <=3.7.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream same-host Ingress reproductionfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo