Traefik: Forwarded alias spoofing top pre-auth decision bypass
traefik
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
traefik
| Product | Affected | Fixed in |
|---|---|---|
| github.com/traefik/traefik/v3 Go |
|
|
| github.com/traefik/traefik/v2 Go |
|
2.11.43| github.com/traefik/traefik Go |
| No fix yet |
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a high severity authentication bypass vulnerability in Traefik's ForwardAuth and snippet-based authentication middleware. Traefik's forwarded-header sanitization logic targets only canonical header names (e.g., X-Forwarded-Proto) and does not strip or normalize alias variants that use underscores instead of dashes (e.g., X_Forwarded_Proto). These unsanitized alias headers are forwarded intact to the authentication backend. When the backend normalizes underscore and dash header forms equivalently, an attacker can inject spoofed trust context — such as a trusted scheme or host — through the alias headers and bypass authentication on protected routes without valid credentials. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.
From the CVE record · GitHub_M
Traefik’s ForwardAuth and snippet-based authentication middleware can pass unsanitized underscore-form forwarded headers to an authentication backend. If the backend treats underscores and dashes equivalently, an attacker can spoof trusted request context and bypass authentication on protected routes without valid credentials or user interaction.
Engineers running Go package github.com/traefik/traefik/v3 in affected ranges >=3.7.0-ea.1 <3.7.0-rc.2 or >=3.0.0-beta1 <3.6.14, github.com/traefik/traefik/v2 before 2.11.43, or github.com/traefik/traefik at any version should check their deployments.