Traefik
Traefik v3.7 Authentication Bypass via TLS Option Conflict
Traefik versions >= v3.7.0 and < v3.7.11 contain an authentication bypass in the Kubernetes Ingress NGINX provider. The TLS option generated for an Ingress carrying the nginx.ingress.kubernetes.io/auth-tls-secret annotation was named after the Ingress namespace and name. As a result, two Ingress objects sharing the same host, the same client CA secret, and the same client-authentication mode produced two distinct TLS option names for that host. Traefik treats this as a TLS options conflict and falls back to the entry point's default TLS configuration, which does not request a client certificate, so a route configured with nginx.ingress.kubernetes.io/auth-tls-verify-client: "on" becomes reachable without a client certificate. Only the v3.7 line is affected; the issue is fixed in v3.7.11.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.7.0, < 3.7.11
Fixed in 3.7.11
Mitigation
Upgrade traefik to 3.7.11 or later.
References
- Vendor advisory github.com/traefik/traefik/security/advisories…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| NVD (tagged exploit) | https://github.com/traefik/traefik/security/advisories/GHSA-j994-9gqj-9hwq | unknown | 20 Nov 2026 |