Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.3amended

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

CVE-2026-54765GHSA-6p8f-p8j2-rqmv

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/traefik/traefik/v3

    Affected
    >= 3.7.0, <= 3.7.5
    Fixed in
    3.7.6

  • Go github.com/traefik/traefik/v2

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Go github.com/traefik/traefik

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.3 · 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 · score source
EPSS
  • CVE-2026-54765: 0.35% estimated exploitation activity in the next 30 days; percentile 28.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary There is a medium severity vulnerability in Traefik's Kubernetes Gateway API provider. When two accepted HTTPRoutes target the same backend Service:port but configure different backendRef filters, Traefik may resolve both routes 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. Patches - https://github.com/traefik/traefik/releases/tag/v3.7.6 For more information If you have any questions or comments about this advisory, please open an issue. <details <summaryOriginal Description</summary Traefik Gateway…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-6p8f-p8j2-rqmv

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6205

  4. Revision 1 · created ·

    Published from osv record GHSA-6p8f-p8j2-rqmv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54765

Advisory: Traefik: Gateway HTTPRoute backendRef filters can leak backend context across routes sharing a Service:port
IDs: CVE-2026-54765, GHSA-6p8f-p8j2-rqmv
Record: https://patchnext.com/advisories/cve-2026-54765 (revision 4, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/traefik/traefik/v3 3.7.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v3: affected >= 3.7.0, <= 3.7.5; fixed in 3.7.6
- Go github.com/traefik/traefik/v2: affected every version
- Go github.com/traefik/traefik: affected every version

## Suggested inspection (read-only)
- Go github.com/traefik/traefik/v3: check the installed version with your package manager.
- Go github.com/traefik/traefik/v2: check the installed version with your package manager.
- Go github.com/traefik/traefik: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/traefik/traefik/v3, github.com/traefik/traefik/v2, github.com/traefik/traefik.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6p8f-p8j2-rqmv (OSV record GHSA-6p8f-p8j2-rqmv lists affected ranges: Go github.com/traefik/traefik/v3 >=3.7.0 <3.7.6 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6205 (OSV record GO-2026-6205 lists affected ranges: Go github.com/traefik/traefik >=0; Go github.com/traefik/traefik/v2 >=0; Go github.com/traefik/traefik/v3 >=3.7.0 <3.7.6 (fixed))
- Verified: https://github.com/advisories/GHSA-6p8f-p8j2-rqmv (GitHub-reviewed advisory GHSA-6p8f-p8j2-rqmv lists affected ranges: Go github.com/traefik/traefik/v3 >=3.7.0 <=3.7.5)

Commands are suggestions: review each one before running it.

Loading voting…