traefik · Traefik · published 2026-07-22
CVE-2026-65602Traefik before 3.6.23 IngressRouteTCP ServersTransport Namespace Bypass
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-65602 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 27% of all CVEs. This Traefik vulnerability: CVSS 5.3 (v4.0). Fixed upstream in Traefik 3.7.7, 3.6.23, 2.11.52. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Traefik 3.7.7, 3.6.23, 2.11.52.
Patch events
Web serverTraefik
Traefik security releases: 3.7.7, 3.6.23, 2.11.52
Upgrade to
3.7.73.6.232.11.52Why: Vendor security release for server software (most severe: CVE-2026-65601).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (27th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v4.0)CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- traefik traefik
3.6.0to before3.6.23(affected)3.6.23(unaffected)
- traefik traefik
3.7.0to before3.7.7(affected)3.7.7(unaffected)
Description (from the CVE record)#
Traefik 3.6.0 through 3.6.22 and 3.7.0 through 3.7.6 fail to enforce the crossProviderNamespaces allowlist for IngressRouteTCP service serversTransport references (the allowlist was only enforced for HTTP serversTransport references). A low-privileged Kubernetes user in a namespace not listed in crossProviderNamespaces can set serversTransport: foo@file on an IngressRouteTCP service, causing Traefik to accept the forbidden cross-provider reference and use a file-provider TCPServersTransport — including privileged backend mTLS client certificates, SPIFFE identity, or PROXY-protocol settings. This is fixed in 3.6.23 and 3.7.7.
Quoted from the CVE Program record.