Traefik 3.7.0-ea.1 before 3.7.15 mTLS Bypass via Ingress NGINX Provider
Traefik 3.7.0-ea.1 through 3.7.14 with the Kubernetes Ingress NGINX provider can silently disable mTLS set via the auth-tls-secret annotation when another Ingress covers the same host. Fixed in 3.7.15.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 3.7.15
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Traefik, a widely used cloud-native reverse proxy and load balancer, is affected when its Kubernetes Ingress NGINX provider is in use. The flaw can silently disable client certificate (mTLS) authentication on routes that require it, allowing unauthenticated users to reach protected backend services.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Traefik from 3.7.0-ea.1 before 3.7.15 contains an authentication bypass vulnerability in the Kubernetes Ingress NGINX provider that silently disables mTLS configured via the auth-tls-secret annotation. When another Ingress declares a path on the same host without matching auth-tls settings, Traefik falls back to default TLS options, letting unauthenticated attackers reach backends requiring client certificates.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- traefik traefik
From 3.7.0-ea.1 · fixed in 3.7.15
References 2
GitHub · traefik/traefik
Questions about CVE-2026-119572
What does this mean?
With the Kubernetes Ingress NGINX provider, mTLS configured through the auth-tls-secret annotation is silently disabled. This lets unauthenticated clients reach backends that are meant to require client certificates.Source: vulncheck.com, github.com
Am I affected, and how do I check?
Traefik versions from 3.7.0-ea.1 before 3.7.15 are affected, in setups that use the Ingress NGINX provider with mTLS set by auth-tls-secret and another Ingress declaring a path on the same host without the same auth-tls settings. Check the Traefik version and whether core.strictTLSOptions is enabled, because enabling it is listed as a condition that prevents the bypass.Source: vulncheck.com, github.com
What should I do about it?
Upgrade Traefik to 3.7.15 or later, which contains the fix. The facts list no workaround.Source: vulncheck.com, github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data