cve.bz

CVE-2026-88009 traefik traefik: HTTP Request Smuggling

8.8 highEPSS 0.4%Fix available

High (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.

On this page
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.

Severity

CVSS 4.0

8.8 high
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

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-09-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-444 Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling)
CWE-1286 Improper Validation of Syntactic Correctness of Input
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
traefik:traefikbefore 2.11.57
traefik:traefikfrom 3.0.0 before 3.7.13

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-f52w-8j3h-j724Gogithub.com/traefik/traefik/v3>=3.0.0 <3.7.133.7.13
GHSA-f52w-8j3h-j724Gogithub.com/traefik/traefik/v2<2.11.572.11.57
GO-2026-6465Gogithub.com/traefik/traefikall versionsno fix published
GO-2026-6465Gogithub.com/traefik/traefik/v2<2.11.572.11.57
GO-2026-6465Gogithub.com/traefik/traefik/v3>=3.0.0 <3.7.133.7.13

Linux distributions

DistributionReleasePackageFixed inAdvisory
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1SUSE-SU-2026:23855-1 SUSE-SU-2026:23863-1
openSUSELeap 16.0govulncheck-vulndb0.0.20260916T180043-160000.1.1openSUSE-SU-2026:21897-1
openSUSETumbleweedtraefik3.7.13-1.1openSUSE-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

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat OpenShift Dev Spaces 3.31devspaces/traefik-rhel9:1792464177Fixed 2026-10-26RHSA-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.

GitHub PoC

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.

  • Boreas37/CVE-2026-88009-PoC Harbor Check: matches CVE 0 stars, Python, created
    CVE-2026-88009 — Traefik forwards a rootless opaque request target that routing/forwardAuth see as '/'. Auth bypass + access-log evasion, v…

Attack patterns (CAPEC)

  • CAPEC-33 HTTP Request Smuggling Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-676 NoSQL Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON