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

> Attackers can bypass path-scoped routing, authorization, and logging in Traefik by sending rootless HTTP/1 request targets, potentially accessing unauthorized resources.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** ECHO-4418-b246-3ebf, GHSA-f52w-8j3h-j724, GO-2026-6465, MINI-8xxv-cmpq-xwpx, MINI-gjmm-f26x-wchj, MINI-p89f-3c69-v3v7

## What is CVE-2026-88009?

CVE-2026-88009 is a high-severity vulnerability in Traefik Traefik, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests), CWE-1286 (Improper Validation of Syntactic Correctness of Input)

## Which versions are affected by CVE-2026-88009?

7 open source packages ship an affected version, including github.com/traefik/traefik/v2, github.com/traefik/traefik and github.com/traefik/traefik/v3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.57 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.57 |
| `github.com/traefik/traefik/v2` | Go | All versions | 2.11.57 |
| `github.com/traefik/traefik` | Go | All versions | None |
| `github.com/traefik/traefik/v3` | Go | From 3.0.0 | 3.7.13 |
| `github.com/traefik/traefik/v3` | Go | From 3.0.0 | 3.7.13 |
| `github.com/traefik/traefik/v3` | Go | From 3.0.0 | 3.7.13 |

Products: Traefik Traefik.

## How do I fix CVE-2026-88009?

Upgrade github.com/traefik/traefik/v2 to 2.11.57 or later.

## Is CVE-2026-88009 being exploited?

There is no known exploitation of CVE-2026-88009 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-88009 — Traefik forwards a rootless opaque request target that routing/forwardAuth see as '/'. Auth bypass + access-log evasion, verified v3.7.10 / v3.7.13. (github_poc): https://github.com/Boreas37/CVE-2026-88009-PoC

## Other vulnerabilities in Traefik Traefik

- [CVE-2024-45410](https://insights.sbomify.com/CVE-2024-45410/): HTTP client can remove the X-Forwarded headers in Traefik (critical 9.8)
- [CVE-2026-88877](https://insights.sbomify.com/CVE-2026-88877/): Traefik v3.7.0 Authentication Bypass via from-to-www-redirect (critical 9.3)
- [CVE-2026-85595](https://insights.sbomify.com/CVE-2026-85595/): Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth (critical 9.3)
- [CVE-2026-88007](https://insights.sbomify.com/CVE-2026-88007/): Traefik HTTP/3 Backend NTLM Connection Reuse (critical 9.1)
- [CVE-2025-32431](https://insights.sbomify.com/CVE-2025-32431/): Traefik has a possible vulnerability with the path matchers (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88009 and fix it if it is affected.

What it is: CVE-2026-88009 is a high-severity vulnerability in Traefik Traefik, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-88009 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.57
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.57
- github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.57
- github.com/traefik/traefik (Go): affected all versions; no fix listed
- github.com/traefik/traefik/v3 (Go): affected from 3.0.0; fixed in 3.7.13
- github.com/traefik/traefik/v3 (Go): affected from 3.0.0; fixed in 3.7.13
- github.com/traefik/traefik/v3 (Go): affected from 3.0.0; fixed in 3.7.13

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-88009/ (Markdown: https://insights.sbomify.com/CVE-2026-88009/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88009
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88009
- OSV: https://osv.dev/vulnerability/CVE-2026-88009

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88009/
Summaries are generated and may contain mistakes; the official description above is the record.