traefik · Traefik · published 2026-07-06
CVE-2026-54765Traefik: Gateway HTTPRoute backendRef filters can leak backend context across routes sharing a Service:port
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-54765 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 28% of all CVEs. This Traefik vulnerability: CVSS 6.3 (v4.0), attacks can be automated, a successful attack gives total control of the component. Fixed upstream in Traefik 3.7.6, 3.6.22, 2.11.51. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Traefik 3.7.6, 3.6.22, 2.11.51.
Patch events
Web serverTraefik
Traefik security releases: 3.7.6, 3.6.22, 2.11.51
Upgrade to
3.7.63.6.222.11.51Why: Vendor security release for server software (most severe: CVE-2026-54763).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (29th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.3 (v4.0)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- traefik traefik
>= 3.7.0, < 3.7.6(affected)
Description (from the CVE record)#
Traefik is an open source HTTP reverse proxy and load balancer. From v3.7.0 prior to v3.7.6, Traefik's Kubernetes Gateway API provider may resolve two accepted HTTPRoutes that target the same backend Service:port but configure different backendRef filters to the same child service and apply only one route's filter set to all requests reaching that backend. In Gateway deployments where backendRef filters set security-sensitive headers, such as tenant identity, authorization context, or values the backend trusts, an attacker who can create an accepted HTTPRoute sharing the same backend Service:port may cause their route's filter context to be applied to another route's requests, potentially crossing namespace boundaries when a ReferenceGrant permits cross-namespace targeting. This issue is fixed in version v3.7.6.
Quoted from the CVE Program record.