Traefik Kubernetes CRD allows unauthorized cross-namespace middleware binding
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
2.11.43| github.com/traefik/traefik Go |
| No fix yet |
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a potential vulnerability in Traefik's Kubernetes CRD provider cross-namespace isolation enforcement. When providers.kubernetesCRD.allowCrossNamespace=false, Traefik correctly rejects direct cross-namespace middleware references from IngressRoute objects, but fails to apply the same restriction to middleware references nested inside a Chain middleware's spec.chain.middlewares[]. An actor with permission to create or update Traefik CRDs in their own namespace can exploit this to cause Traefik to resolve and apply middleware objects from another namespace, bypassing the documented isolation boundary. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.
From the CVE record · GitHub_M
Traefik's Kubernetes CRD provider does not enforce cross-namespace isolation for middleware references nested in a Chain middleware when allowCrossNamespace=false. An actor permitted to create or update Traefik CRDs in their own namespace can cause Traefik to apply middleware from another namespace.
Teams running affected versions of the Go packages github.com/traefik/traefik/v3, github.com/traefik/traefik/v2, or github.com/traefik/traefik should check their deployments.