Advisory record · GHSA-6p8f-p8j2-rqmv

Traefik: Gateway HTTPRoute backendRef filters can leak backend context across routes sharing a Service:port

CVSS 6.3 MediumEPSS 0.0035 · 28th percentile

Published by the GitHub Advisory Database at 6 Aug 2026, 16:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/traefik/traefik/v3Go>=3.7.0, <3.7.63.7.6
Identifiers
GHSA-6p8f-p8j2-rqmv · CVE-2026-54765 · GO-2026-6205
Weakness (CWE)
CWE-284 · CWE-863
Published
6 Aug 2026
Updated
18 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Traefik versions 3.7.0 up to but not including 3.7.6 can apply one HTTPRoute's backendRef filters to another route's requests when both routes target the same backend Service and port with different filters. An attacker who can create an accepted HTTPRoute that targets the same Service and port can cause their route's filter context, such as headers the backend trusts, to be applied to another route's traffic, potentially across namespaces when a ReferenceGrant allows it. Upgrade to Traefik 3.7.6, which fixes the issue.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 4.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 (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0035, the 28th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 1 Jul 2026, 15:21 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:52 UTC First seen by agentprime
  3. 31 Oct 2026, 14:52 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.