Traefik
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in any Traefik product.
RSS Feeds for Traefik security vulnerabilities
Create a CVE RSS feed including security vulnerabilities found in Traefik products with stack.watch. Just hit watch, then grab your custom RSS feed url.
Products by Traefik Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2026 there have been 62 vulnerabilities in Traefik with an average score of 7.1 out of ten. Last year, in 2025 Traefik had 5 security vulnerabilities published. That is, 57 more vulnerabilities have already been reported in 2026 as compared to last year. However, the average CVE base score of the vulnerabilities in 2026 is greater by 1.18.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 62 | 7.08 |
| 2025 | 5 | 5.90 |
| 2024 | 4 | 7.50 |
| 2023 | 5 | 6.98 |
| 2022 | 4 | 7.00 |
| 2021 | 1 | 8.10 |
| 2020 | 3 | 4.70 |
| 2019 | 1 | 0.00 |
| 2018 | 1 | 0.00 |
It may take a day or so for new Traefik vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Traefik Security Vulnerabilities
| CVE | Date | Vulnerability | Products |
|---|---|---|---|
| CVE-2026-121966 | Nov 04, 2026 |
Traefik 2.x < 2.11.60 & 3.x < 3.7.16: Auth Pool NTLM/Negotiate ID LeakTraefik 2.x before 2.11.60 and 3.x before 3.7.16 sends ForwardAuth subrequests (and, in 3.7, Ingress NGINX auth-url requests) through an auth-server connection pool shared by all clients, exposing connection-bound NTLM or Negotiate authentication. An unauthenticated attacker can reuse another user's authenticated connection, receiving the victim's identity via authResponseHeaders to access backends as that user. |
|
| CVE-2026-119574 | Oct 30, 2026 |
Traefik 3.2.03.7.14 FastProxy data race causing DoSTraefik from 3.2.0 before 3.7.15 contains a data race in the experimental FastProxy that allows unauthenticated attackers to crash the process by abusing HTTP/1 protocol upgrades. Attackers can repeatedly open and abort upgraded connections such as WebSocket, corrupting the unsynchronized shared bufio.Reader and triggering an unrecovered panic that terminates Traefik. |
|
| CVE-2026-119573 | Oct 30, 2026 |
Traefik 3.7.11-3.7.14 AuthTLS Secret CrossNamespace BypassTraefik 3.7.11 before 3.7.15 contains an authorization bypass in the Kubernetes Ingress NGINX provider that skips the cross-namespace check on the auth-tls-secret annotation when a cached client authentication TLS option is reused. Users who can create Ingresses can reference another namespace's CA secret already used by another Ingress, enforcing it on their own routes and learning whether it exists, without disclosure of its contents. |
|
| CVE-2026-119572 | Oct 30, 2026 |
Traefik <3.7.15 authtls-secret mTLS bypass in K8s Ingress NGINXTraefik 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. |
|
| CVE-2026-114656 | Oct 22, 2026 |
Traefik <2.11.58 / <3.7.13 Auth Bypass via Host MatcherTraefik before 2.11.58 and 3.7.13 contains an authentication bypass vulnerability that allows unauthenticated clients to skip client-certificate checks because negated Host matchers are counted as served domains. Attackers can reach backends protected by RequireAndVerifyClientCert when a router rule with !Host() creates a TLS options conflict that falls back to the default options. |
|
| CVE-2026-114641 | Oct 22, 2026 |
Traefik 2.11.x<2.11.58 & 3.x<3.7.14 Race Cond in NTLM/Kerb AuthTraefik 2.11.x before 2.11.58 and 3.x before 3.7.14 contains a race condition in NTLM and Kerberos (Negotiate) backend authentication, where the per-connection sticky round tripper slot is read and written without synchronization. Remote attackers can send concurrent HTTP/2 or HTTP/3 requests over one connection to orphan backend connections, break connection-bound authentication, or crash Traefik. |
|
| CVE-2026-114642 | Oct 22, 2026 |
Traefik 2.11 <2.11.58 & 3.0 <3.7.14 TLS client config reuse (NTLM/Kerberos)Traefik 2.11.0 before 2.11.58 and 3.0.0 before 3.7.14 stores its NTLM/Kerberos backend round tripper in a client-connection slot not keyed by ServersTransport, so one service's TLS client configuration is reused for another service's backend. An unauthenticated client can arm the slot via a backend issuing an NTLM or Negotiate challenge, then reach another service on the same keep-alive connection, bypassing its root CAs, server name, and certificate verification. |
|
| CVE-2026-114640 | Oct 22, 2026 |
Traefik <3.7.14 authTLS bypass via Ssl-Client-* headers (K8s Ingress)Traefik from v3.7.0 before v3.7.14 contains an authentication bypass vulnerability in its Kubernetes Ingress-NGINX provider that forwards client-supplied Ssl-Client-* headers on the plaintext HTTP router. When ssl-redirect is disabled alongside auth-tls-pass-certificate-to-upstream, unauthenticated attackers can send Ssl-Client-Verify: SUCCESS with a chosen certificate subject and issuer to impersonate mTLS identities. |
|
| CVE-2026-114638 | Oct 22, 2026 |
Traefik <3.7.14 AuthTLS Secret Collision Leads to Auth Bypass (K8s Ingress)Traefik v3.7.0 before v3.7.14 contains an improper authentication vulnerability in the Kubernetes Ingress NGINX provider that merges client CAs when auth-tls-secret names collide after dot-to-dash normalization. Attackers holding certificates from another host's CA can access a host requiring its own client CA, while that host's legitimate clients are refused. |
|
| CVE-2026-114639 | Oct 22, 2026 |
Traefik <2.11.58 & <3.7.14 Auth Bypass via Shared Conn PoolTraefik 2.11.0 before 2.11.58 and 3.0.0 before 3.7.14 contains an authentication bypass because a first request preauthenticated with an Authorization: Negotiate token authenticates a socket in the globally shared backend connection pool, which is never isolated. Unauthenticated attackers on separate frontend connections can be assigned that NTLM/Kerberos-bound socket and perform reads or writes with the victim's identity. |
|