Traefik before 2.11.46, 3.6.17, and 3.7.1 Cross-Namespace Resource Reference via Kubernetes Annotations
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| traefik traefik |
|
|
| traefik traefik |
|
|
| traefik traefik |
|
|
traefik
| Product | Affected | Fixed in |
|---|---|---|
| traefik traefik |
|
|
| traefik traefik |
|
|
| traefik traefik |
|
|
Traefik before 2.11.46, 3.x before 3.6.17, and 3.7.0 lack namespace validation for Ingress and Service annotations in the Kubernetes Ingress provider, allowing references to Middlewares, ServersTransports, and TLSOptions in other namespaces. Attackers able to create or update Ingress or Service resources in one namespace can set router.middlewares or service.serverstransport annotations to obtain another tenant's injected credentials or reuse its client certificates, bypassing namespace-based tenant isolation.
From the CVE record · VulnCheck
Traefik’s Kubernetes Ingress provider does not validate namespaces in Ingress and Service annotations. An attacker able to create or update those resources in one namespace can reference another tenant’s Middlewares or ServersTransports to obtain injected credentials or reuse client certificates, bypassing namespace-based tenant isolation.
Check Traefik deployments using the Kubernetes Ingress provider on versions before 2.11.46, 3.x before 3.6.17, or 3.7.0.