Live › vulnerability › CVE-2026-112778
Go to dashboardTraefik's Kubernetes Ingress provider does not check namespaces when Ingress or Service annotations reference Middlewares, ServersTransports, or TLSOptions. A user who can create or update Ingress or Service resources in one namespace can reuse another tenant's injected credentials or client certificates.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| traefik | vendor | < 2.11.46 | 2.11.46 |
| traefik | vendor | >= 3.0.0, < 3.6.16 | 3.6.16 |
| traefik | vendor | = 3.7.0 | – |
2.11.46, 3.x below 3.6.17, and 3.7.02.11.46 or 3.6.17 or later3.7.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-112778")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.