Quick answers
- Is CVE-2026-88008 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88008 being exploited in the wild.
- How severe is CVE-2026-88008?
- Critical severity, with a CVSS score of 9.1, published 10 September 2026.
- Which products and versions are affected?
- github.com/traefik/traefik (Go) SEMVER:introduced=0; github.com/traefik/traefik/v2 (Go) >= 2.11.26, < 2.11.57, SEMVER:introduced=2.11.26,fixed=2.11.57; github.com/traefik/traefik/v3 (Go) >= 3.4.2, < 3.7.13, SEMVER:introduced=3.4.2,fixed=3.7.13; Traefik v2.11.26 to v2.11.56, v3.4.2 to v3.6.x.
- Is there a fix for CVE-2026-88008?
- Yes. github.com/traefik/traefik/v2 (Go): upgrade to 2.11.57 or later; github.com/traefik/traefik/v3 (Go): upgrade to 3.7.13 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-88008 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-88008?
- Check whether you run github.com/traefik/traefik (Go), github.com/traefik/traefik/v2 (Go), github.com/traefik/traefik/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/traefik/traefik/v2 (Go): upgrade to 2.11.57 or later
go get github.com/traefik/traefik/v2@v2.11.57 - github.com/traefik/traefik/v3 (Go): upgrade to 3.7.13 or later
go get github.com/traefik/traefik/v3@v3.7.13
Technical details
This is an HTTP request smuggling vulnerability in Traefik's HTTP reverse proxy layer. The root cause is the unrestricted forwarding of client-supplied `Connection: Upgrade` and `Upgrade: <token>` headers to backend services. When a backend accepts an h2c upgrade (triggered by `Upgrade: h2c` and `HTTP2-Settings` headers) and responds with `101 Switching Protocols`, Traefik's reverse proxy (net/http/httputil.ReverseProxy) enters tunnel mode, copying raw bytes between client and backend without further HTTP parsing or middleware enforcement. The vulnerability occurs because: (1) Traefik forwards upgrade tokens without validating they are explicitly supported (only WebSocket should be allowed for HTTP protocol upgrades), (2) after receiving a 101 response, the routing/middleware chain is no longer applied to subsequent requests on that connection, and (3) an attacker can establish the tunnel through an unprotected router and send HTTP/2 requests to protected paths via the same backend connection. The attack requires a backend that honors h2c upgrades without strict validation of the HTTP/1.1 Connection header. Patches are available in v2.11.57 and v3.7.13, which strip the `Upgrade: h2c` and `HTTP2-Settings` headers before forwarding, while preserving legitimate WebSocket upgrades.
Affected products
- Traefik Traefik v2.11.26 to v2.11.56, v3.4.2 to v3.6.x
Identifiers
- CVE-2026-88008
- GHSA-w4v4-9rw7-5326
- GO-2026-6468
Timeline
- 2026-09-07: disclosed: Vulnerability disclosed in GitHub Advisory GHSA-w4v4-9rw7-5326
- 2026-09-10: patched: Patches released: Traefik v2.11.57 and v3.7.13