CVE-2026-88009 json
Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging
published 2026-09-10 59 d ago modified 2026-09-17 52 d ago also GHSA-f52w-8j3h-j724 , GO-2026-6465 , EUVD-2026-75578
- cvss
- 8.2
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
Traefik is an open source HTTP reverse proxy and load balancer. Prior to 2.11.57, and 3.7.13, Traefik accepts a rootless HTTP/1 request target that Go stores in URL.Opaque while leaving URL.Path empty. The rewriteRequestBuilder path evaluates routing, path sanitization, forwardAuth, encodedCharacters, and access logging against a path normalized to / but forwards URL.Opaque verbatim to the backend, allowing cross-vhost routing bypass, path-scoped authorization bypass, and access-log evasion when the backend interprets the opaque target as a path. This issue is fixed in 2.11.57 and 3.7.13.
Patch / fix
- go github.com/traefik/traefik/v3 3.7.13
- go github.com/traefik/traefik/v2 2.11.57
- traefik traefik 2.11.57, 3.7.13
- govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260916T180043-160000.1.1
suse advisories SUSE-SU-2026:23855-1SUSE-SU-2026:23863-1
- traefik openSUSE Tumbleweed 3.7.13-1.1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260916T180043-160000.1.1
opensuse advisories openSUSE-SU-2026:12076-1openSUSE-SU-2026:21897-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-88009 updated cvss 8.2
github.com/traefik/traefik: Traefik: Authorization bypass and access-log evasion via crafted HTTP/1 request
-
Red Hat OpenShift Dev Spaces 3.31 devspaces/traefik-rhel9 1792464177fixed: vendor fix RHSA-2026:90321
-
Red Hat OpenShift Dev Spaces 3.31 devspaces/udi-rhel9 1792708612, devspaces/code-rhel9 1792599388, devspaces/server-rhel9 1792775639, devspaces/openvsx-rhel9 1792494821, devspaces/udi-base-rhel9 1792686842, devspaces/code-sshd-rhel9 1792598059, +9 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 59 d ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 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 |
| CNA | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/traefik/traefik/v3 | >=3.0.0, <3.7.13 |
3.7.13 |
| go | github.com/traefik/traefik/v2 | <2.11.57 |
2.11.57 |
| go | github.com/traefik/traefik | all versions |
no fix listed |
Affected products
- traefik traefik
Classification
References
-
github.com
/traefik/traefik/pull/13796
web, issue-tracking, patch
-
github.com
/traefik/traefik/commit/58d1e9ca204526823211e30fd4634101c59d58e9
web, patch
-
github.com
/traefik/traefik/security/advisories/GHSA-f52w-8j3h-j724
web, patch, vendor-advisory, advisory
-
github.com
/traefik/traefik/releases/tag/v2.11.57
web, release-notes
-
github.com
/traefik/traefik/releases/tag/v3.7.13
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-88009
advisory
-
github.com
/traefik/traefik
package
Sources
- CVE List CVE-2026-88009
- GitHub Advisory GHSA-f52w-8j3h-j724
- NVD CVE-2026-88009
- OSV GO-2026-6465
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.