# Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging Advisory record · `GHSA-f52w-8j3h-j724` - **Identifiers:** `GHSA-f52w-8j3h-j724` · `CVE-2026-88009` · `GO-2026-6465` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** No - **Weakness (CWE):** [CWE-444](https://cwe.mitre.org/data/definitions/444.html) · [CWE-1286](https://cwe.mitre.org/data/definitions/1286.html) - **Tags:** [HTTP request smuggling](https://agentprime.io/advisories/tag/request-smuggling.md) · [CWE-1286](https://agentprime.io/advisories/tag/cwe-1286.md) - **Published:** 10 Sept 2026 - **Updated:** 17 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 10 Sept 2026, 23:03 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/traefik/traefik/v3` (Go): affected `>=3.0.0, <3.7.13`; fixed in `3.7.13` - `github.com/traefik/traefik/v2` (Go): affected `<2.11.57`; fixed in `2.11.57` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Traefik v3 (>=3.0.0, <3.7.13) and Traefik v2 (<2.11.57) are affected. A remote, unauthenticated client can send an HTTP/1.x request with a rootless request-target, which Traefik routes and enforces guards against as path "/" while forwarding the original target unchanged to the backend. This can bypass host-based routing, path-scoped middleware and authorization, and access logging. Upgrade Traefik v3 to 3.7.13 or Traefik v2 to 2.11.57; the source lists no workaround. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 8.8 High, CVSS 4.0: `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`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0044, the 38th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:13 UTC: First seen by agentprime - 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-f52w-8j3h-j724) ## Sources - [GitHub Advisory Database: GHSA-f52w-8j3h-j724](https://github.com/advisories/GHSA-f52w-8j3h-j724) - [OSV: GHSA-f52w-8j3h-j724](https://osv.dev/vulnerability/GHSA-f52w-8j3h-j724) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .