GHSA-6jwx-7vp4-9847: Traefik has an StripPrefixRegex Middleware Authorization Bypass via Path/RawPath Desync
SummaryThere is a high severity authentication bypass vulnerability in Traefik's `StripPrefixRegex` middleware when used in combination with `ForwardAuth`, `BasicAuth`, or `DigestAuth`.The middleware matches the regex against the decoded URL path but uses the resulting byte length to slice the percent-encoded raw path. When a dot (or multiple dots) appears in the prefix portion of the URL, the raw path after stripping becomes a dot-segment (e.g. `/./admin/secret`).`ForwardAuth` receives this dot-segment path in `X-Forwarded-Uri`, which does not match the protected path patterns and therefore allows the request through. The backend then normalizes the dot-segment to the real path per RFC 3986 and serves the protected contentAn unauthenticated attacker can exploit this against any backend that performs dot-segment normalization.Patcheshttps://github.com/traefik/traefik/releases/tag/v2.11.43https://github.com/traefik/traefik/releases/tag/v3.6.14https://github.com/traefik/traefik/releases/tag/v3.7.0-rc.2For more informationIf there are any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).SummaryStripPrefixRegex uses the byte length of a decoded Path match to slice the encoded RawPath. When percent-encoded characters are in the prefix region, this produces a wrong RawPath. ForwardAuth then
  receives this wrong path in X-Forwarded-Uri, sees a path that doesn't match its protection rules, and approves the request. The backend serves protected content.Details`pkg/middlewares/stripprefixregex/strip_prefix_regex.go`, line 62:prefix comes from matching the regex against the decoded req.URL.Path (line 51). len(prefix) is then used to index into the encoded req.URL.RawPath. These lengths don't match when percent-encoding is
  present.Example with regex ^/api:GET /api%20/admin/secretDecoded Path: /api /admin/secret -> prefix = /api (4 bytes)Encoded RawPath: /api%20/admin/secret -> same region is 6 bytesRawPath[4:] = %20/admin/secret -> after ensureLeadingSlash -> /%20/admin/secretForwardAuth sees X-Forwarded-Uri: /%20/admin/secret -> not /admin/* -> allows itBackend serves the protected admin contentPoCRequires Docker and Docker Compose. I have a setup that runs Traefik v3.6.11 with StripPrefixRegex + ForwardAuth + a backend. It sends a normal request (blocked, 403) and an encoded request (bypasses
  auth, 200, returns protected data). Can share the files here if useful.ImpactAuth bypass. Any path protected by ForwardAuth, BasicAuth, or DigestAuth can be accessed without credentials when StripPrefixRegex is in the same middleware chain. The attacker only needs to add a
  percent-encoded character to the prefix portion of the URL.Updated PoC (reporter follow-up)After further testing, the confirmed working exploit uses `%2e` (percent-encoded dot) rather than `%20`. Dot-segment normalization (`/./` -> `/`) is RFC 3986 standard behavior handled automatically by Express.js, Go's `http.ServeMux`, Spring Boot, and others — no custom configuration needed.Chain:Results (Traefik v3.6, unmodified Express.js express.static):Auth server logs:Reproduction:
CVSS v4.0: 7.8
CVSS v3.1: 8.2