Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

Traefik: Gateway API route identity collision allows cross-namespace backend hijacking

CVE-2026-71327GHSA-fgjj-px3w-67xx

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.0.0, < 3.6.25>= 3.7.0, < 3.7.10
    Fixed in
    3.7.10, 3.6.25

  • 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
8.2 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-71327: 0.48% estimated exploitation activity in the next 30 days; percentile 41.53 (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 high severity vulnerability in Traefik's Kubernetes Gateway API provider. Router and service identities for HTTPRoute, GRPCRoute, TCPRoute and TLSRoute objects were built by hyphen-concatenating the route namespace, the route name, the Gateway identity, the entry point and the rule index, a construction that is not injective because Kubernetes names may themselves contain hyphens. Two distinct Routes attached to the same Gateway with equivalent match rules can therefore produce the same identity, and the Route loaded later silently overwrites the earlier one, so a tenant able to create an accepted Route in a colliding namespace/name combination can redirect another namespace's traffic to a backend it controls. All Traefik v3 minor lines are affected; the lines older than v3.6 are no longer maintained and will not receive a patch of their own, so users running them should upgrade to a maintained, patched release. Patches -…

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

    Amended from ghsa record GHSA-fgjj-px3w-67xx

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6209

  3. Revision 1 · created ·

    Published from osv record GHSA-fgjj-px3w-67xx

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-71327

Advisory: Traefik: Gateway API route identity collision allows cross-namespace backend hijacking
IDs: CVE-2026-71327, GHSA-fgjj-px3w-67xx
Record: https://patchnext.com/advisories/cve-2026-71327 (revision 3, 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: High (CVSS 8.2)
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.10, 3.6.25. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v3: affected >= 3.0.0, < 3.6.25; >= 3.7.0, < 3.7.10; fixed in 3.7.10, 3.6.25
- 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-fgjj-px3w-67xx (OSV record GHSA-fgjj-px3w-67xx lists affected ranges: Go github.com/traefik/traefik/v3 >=3.0.0 =3.7.0 <3.7.10 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6209 (OSV record GO-2026-6209 lists affected ranges: Go github.com/traefik/traefik >=0; Go github.com/traefik/traefik/v2 >=0; Go github.com/traefik/traefik/v3 >=3.0.0 =3.7.0 <3.7.10 (fixed))
- Verified: https://github.com/advisories/GHSA-fgjj-px3w-67xx (GitHub-reviewed advisory GHSA-fgjj-px3w-67xx lists affected ranges: Go github.com/traefik/traefik/v3 >=3.0.0 =3.7.0 <3.7.10)

Commands are suggestions: review each one before running it.

Loading voting…