Skip to content

← Actionable
High, CVSS 8.8amended

Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging

CVE-2026-88009GHSA-f52w-8j3h-j724

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.

Affected packages

  • Go github.com/traefik/traefik/v3

    Affected
    >= 3.0.0, < 3.7.13
    Fixed in
    3.7.13
  • Go github.com/traefik/traefik/v2

    Affected
    < 2.11.57
    Fixed in
    2.11.57
  • 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
8.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-88009: 0.44% estimated exploitation activity in the next 30 days; percentile 38.62 (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 Traefik accepts an HTTP/1.x request whose request-target is in rootless / opaque form (for example GET http:http://internal-vhost/admin HTTP/1.1). Go parses this into URL.Opaque with an empty URL.Path, so Traefik evaluates all routing, path-sanitization, middleware and access-log decisions against a path that normalizes to /, while the proxy forwards the attacker's original target byte-for-byte to the backend. Router path/prefix guards, forwardAuth path-scoped policies and the encodedCharacters hardening never see the real target, and the access log records every such request as GET / HTTP/1.1. Against a backend that resolves a rootless target as a path, this yields cross-vhost routing bypass, path-scoped authorization bypass and access-log evasion — unauthenticated, with stock entrypoint defaults. Traefik v3.0 through v3.6 are end-of-life and are also affected; they will not receive a fix on their own line. Users on those versions must upgrade to v3.7.13. Patches -…

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

    Amended from ghsa record GHSA-f52w-8j3h-j724

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

  4. Revision 1 · created ·

    Published from osv record GHSA-f52w-8j3h-j724

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

Advisory: Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging
IDs: CVE-2026-88009, GHSA-f52w-8j3h-j724
Record: https://patchnext.com/advisories/cve-2026-88009 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
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.13; github.com/traefik/traefik/v2 2.11.57. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v3: affected >= 3.0.0, < 3.7.13; fixed in 3.7.13
- Go github.com/traefik/traefik/v2: affected < 2.11.57; fixed in 2.11.57
- 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-f52w-8j3h-j724 (OSV record GHSA-f52w-8j3h-j724 lists affected ranges: Go github.com/traefik/traefik/v3 >=3.0.0 =0 <2.11.57 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6465 (OSV record GO-2026-6465 lists affected ranges: Go github.com/traefik/traefik >=0; Go github.com/traefik/traefik/v2 >=0 =3.0.0 <3.7.13 (fixed))
- Verified: https://github.com/advisories/GHSA-f52w-8j3h-j724 (GitHub-reviewed advisory GHSA-f52w-8j3h-j724 lists affected ranges: Go github.com/traefik/traefik/v3 >=3.0.0 =0 <2.11.57)

Commands are suggestions: review each one before running it.

Loading voting…