All vulnerabilities

Servers and applications

GHSA-cp28-5662-543f

sanitizePath does not remove path-parameter dot-segments (/..;x/), enabling path-based authorization bypass

Severity
High 7.8
Published
12 Nov 2026
Last changed
12 Nov 2026
Added to UpHeron
12 Nov 2026
Fixed in
2.11.62, 3.7.18, 3.8.0-rc.2
Weakness
Path traversal (CWE-22)CWE-436
Attack
Over the network · No login needed · No user action needed
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N
Sources
Project advisories (GitHub)

Description

There is a vulnerability in Traefik's request path sanitization. The sanitizePath entry point option, enabled by default, resolves the .. and . dot-segments and removes the duplicate slashes from the request path before routing, but it leaves a dot-segment carrying a path parameter, such as /..;x/, untouched. Traefik matches its routers and applies its middlewares on this unresolved path and forwards it unchanged. When a backend that strips path parameters (Servlet containers, Spring, ...) is shared between an unauthenticated router and a router protected by an authentication or authorization middleware, an unauthenticated attacker can send a single request such as /public/..;x/admin to reach the protected resources and bypass the middleware.

Traefik v2.11.62, v3.7.18 and v3.8.0-rc.2 resolve the .., . and empty segments carrying path parameters before the dot-segment removal, when sanitizePath is enabled (the default).

From traefik/traefik's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
TraefikServers and applications · github:traefik/traefik
  • Every version before 2.11.62
  • From 3.0.0 before 3.7.18
  • From 3.8.0-rc.1 before 3.8.0-rc.2

References