CVSS 4.0
8.8 highCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NHigh (8.8) in traefik traefik. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/traefik/traefik/v3 3.7.13.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:Ngithub.com/traefik/traefik/v3 (Go): fixed in 3.7.13github.com/traefik/traefik/v2 (Go): fixed in 2.11.57Explain CVE-2026-88009 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-88009?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-88009?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-88009 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| traefik:traefik | before 2.11.57 |
| traefik:traefik | from 3.0.0 before 3.7.13 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-f52w-8j3h-j724 | Go | github.com/traefik/traefik/v3 | >=3.0.0 <3.7.13 | 3.7.13 |
| GHSA-f52w-8j3h-j724 | Go | github.com/traefik/traefik/v2 | <2.11.57 | 2.11.57 |
| GO-2026-6465 | Go | github.com/traefik/traefik | all versions | no fix published |
| GO-2026-6465 | Go | github.com/traefik/traefik/v2 | <2.11.57 | 2.11.57 |
| GO-2026-6465 | Go | github.com/traefik/traefik/v3 | >=3.0.0 <3.7.13 | 3.7.13 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | govulncheck-vulndb | 0.0.20260916T180043-160000.1.1 | SUSE-SU-2026:23855-1 SUSE-SU-2026:23863-1 |
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260916T180043-160000.1.1 | openSUSE-SU-2026:21897-1 |
| openSUSE | Tumbleweed | traefik | 3.7.13-1.1 | openSUSE-SU-2026:12076-1 |
From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: SUSE · openSUSE.
Red Hat rates this Important.
A flaw was found in Traefik's HTTP/1 request handling. Prior to versions 2.11.57 and 3.7.13, Traefik processes rootless HTTP/1 request targets by storing them in Go's URL.Opaque field while leaving URL.Path empty. During request processing, the rewriteRequestBuilder path normalizes the routing, path-scoped authorization, forwardAuth, and access logging paths to "/" while forwarding the original opaque target verbatim to the backend. A remote, unauthenticated attacker can craft requests with rootless HTTP/1 targets to bypass cross-vhost routing rules, path-scoped access controls, and access logging when the backend interprets the opaque string as a valid path.
There is no effective configuration-level or path-sanitization mitigation within Traefik to resolve this issue, as request normalization occurs prior to routing and forwarding decisions. System administrators should upgrade Traefik to version 2.11.57, 3.7.13, or later, or deploy an upstream reverse proxy to sanitize or reject HTTP/1 requests containing rootless or opaque request targets before they reach Traefik.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Dev Spaces 3.31 | devspaces/traefik-rhel9:1792464177 | Fixed 2026-10-26 | RHSA-2026:90321 |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-88009.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.