Traefik from 2.11.58 before 2.11.61 contains a resource leak vulnerability that allows unauthenticated attackers to exhaust resources by sending Authorization headers with NTLM or Negotiate schemes. Attackers can open many short-lived connections that each allocate a dedicated backend transport never released, exhausting memory, file descriptors and backend connections.
CVE-2026-121966 is a vulnerability in Traefik versions 2.x before 2.11.60 and 3.x before 3.7.16. It involves the exposure of authenticated user data due to shared connection pools for ForwardAuth subrequests and Ingress NGINX auth-url requests. An unauthenticated attacker can reuse another user's authenticated connection and gain access to backend services as that user.
Traefik versions from 3.2.0 up to but not including 3.7.15 contain a data race vulnerability in the experimental FastProxy feature. This flaw allows unauthenticated attackers to crash the Traefik process by abusing HTTP/1 protocol upgrades, such as repeatedly opening and aborting upgraded connections like WebSocket. The unsynchronized access to shared bufio.Reader leads to a panic that terminates the service.
Traefik versions 3.7.11 through 3.7.14 contain an authorization bypass vulnerability in the Kubernetes Ingress NGINX provider. This flaw allows users with permission to create Ingress resources to bypass cross-namespace authorization checks on the auth-tls-secret annotation by reusing a cached client authentication TLS option. As a result, such users can reference a CA secret from another namespace already used by another Ingress, enforcing it on their own routes and determining the secret's existence without accessing its contents. The issue is fixed in version 3.7.15.
CVE-2026-119572 is an authentication bypass vulnerability in Traefik versions 3.7.0-ea.1 through before 3.7.15. The flaw affects the Kubernetes Ingress NGINX provider where mTLS configured via the auth-tls-secret annotation can be silently disabled. This occurs when another Ingress on the same host declares a path without matching auth-tls settings, causing Traefik to fall back to default TLS options and allowing unauthenticated access to backends that require client certificates.
Traefik versions prior to 2.11.58 and 3.7.13 contain an authentication bypass vulnerability caused by an interpretation conflict with negated Host matchers. This flaw allows unauthenticated clients to bypass client-certificate verification due to a TLS options conflict fallback. The issue is resolved in versions 2.11.58 and 3.7.13.
CVE-2026-114642 is a vulnerability in Traefik versions 2.11.0 before 2.11.58 and 3.0.0 before 3.7.14. It involves improper certificate validation due to reuse of TLS client configurations across backend services. An unauthenticated client can exploit this to bypass TLS verification, including root CA checks and server name validation, potentially compromising secure connections between services.
CVE-2026-114641 is a race condition vulnerability in Traefik versions 2.11.x before 2.11.58 and 3.x before 3.7.14. It affects the NTLM and Kerberos (Negotiate) backend authentication mechanisms by improperly synchronizing access to a per-connection sticky round tripper slot. This flaw allows remote attackers to send concurrent HTTP/2 or HTTP/3 requests over a single connection, potentially orphaning backend connections, breaking connection-bound authentication, or causing Traefik to crash.
Traefik versions from 3.7.0 up to but not including 3.7.14 have an authentication bypass vulnerability in the Kubernetes Ingress-NGINX provider. This flaw allows unauthenticated attackers to spoof mTLS identities by sending crafted Ssl-Client-* headers when ssl-redirect is disabled and auth-tls-pass-certificate-to-upstream is enabled.
CVE-2026-114639 is an authentication bypass vulnerability in Traefik affecting versions 2.11.0 through 2.11.57 and 3.0.0 through 3.7.13. The issue occurs because sockets authenticated with an Authorization: Negotiate token are stored in a globally shared backend connection pool without proper isolation. This flaw allows unauthenticated attackers on separate frontend connections to reuse an authenticated socket and perform actions with the victim's identity. The vulnerability has a high severity rating and a CVSS 4.0 score of 7. A fix is available in Traefik versions 2.11.58 and 3.7.14.
Traefik versions 3.7.0 through 3.7.13 have an improper authentication vulnerability in the Kubernetes Ingress NGINX provider. This flaw occurs due to merging client certificate authorities (CAs) when auth-tls-secret names collide after dot-to-dash normalization. As a result, attackers with certificates from a different host's CA can gain unauthorized access to hosts that require their own client CA, while legitimate clients of those hosts are denied access. The issue is fixed in version 3.7.14.
Traefik versions from 3.2.0 up to but not including 3.7.14 contain an authentication bypass vulnerability in the experimental FastProxy connection pool. This flaw allows unauthenticated clients to receive backend connections authenticated by other users via NTLM or Negotiate protocols, potentially exposing sensitive data and allowing actions on behalf of the victim.
Traefik versions 3.7.13 before 3.7.14 have an access-control bypass vulnerability in the Kubernetes Ingress NGINX provider. The HTTP router generated for ssl-passthrough Ingresses on non-TLS entry points does not enforce access-control annotations, allowing unauthenticated attackers to access protected backends without logging.
Traefik versions before 2.11.58 and 3.7.14 contain an authentication bypass vulnerability related to the SNI check. This issue arises when the TLS state of a request is nil, allowing unauthenticated clients to send HTTP/2 requests with the :scheme http pseudo-header over TLS on Go 1.27 builds. This bypass can grant access to routers that require client certificates without presenting one.
CVE-2026-112778 is a vulnerability in Traefik versions before 2.11.46, 3.x before 3.6.17, and 3.7.0 that allows attackers with permissions to create or update Ingress or Service resources in one Kubernetes namespace to reference Middlewares, ServersTransports, and TLSOptions in other namespaces. This bypasses namespace-based tenant isolation, potentially exposing another tenant's injected credentials or client certificates.
A timing discrepancy vulnerability exists in Traefik versions 3.6.11 through 3.7.12 in the BasicAuth middleware. This flaw allows an attacker to determine whether a username exists by observing timing differences in authentication attempts. The issue does not disclose passwords or bypass authentication and is fixed in version 3.7.13.
Traefik versions 3.7.0 through 3.7.10 contain an authentication bypass vulnerability in the Kubernetes Ingress NGINX provider. The issue arises from how TLS options are named for Ingress objects with the auth-tls-secret annotation, causing Traefik to fallback to a default TLS configuration that does not enforce client certificate verification. This allows routes configured to require client certificates to be accessed without one. The vulnerability is fixed in version 3.7.11.
A vulnerability in Traefik's Kubernetes Gateway API provider prior to versions 2.11.46, 3.6.17, and 3.7.1 allows a tenant with HTTPRoute creation permissions to bypass security settings and expose the REST provider handler. This enables unauthorized dynamic configuration write access to Traefik, allowing reconfiguration of routers and services. The issue is fixed in the specified versions.
Traefik versions prior to 2.11.44, 3.6.15, and 3.7.0-rc.3 contain an information disclosure vulnerability in the errors middleware. This flaw causes the middleware to forward the full original request headers, including sensitive authentication data like Authorization and Cookie headers, to a separate error page service when backend responses match certain status codes. This behavior is undocumented and may lead to unintended exposure of credentials to infrastructure components not meant to receive them. The issue is fixed in versions 2.11.44, 3.6.15, and 3.7.0-rc.3.
A timing side-channel vulnerability in Traefik's BasicAuth middleware prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2 allows attackers to enumerate valid usernames by measuring authentication response times. The issue arises because a variable intended for a constant-time fallback secret is empty, causing the comparison to short-circuit quickly and reveal timing differences. This vulnerability has been patched in the specified versions.