Traefik Vulnerable to BasicAuth/DigestAuth Identity Spoofing via Non-Canonical headerField
Published 27 Mar 2026 · Updated 4 Nov 2026
Is your project on an affected github.com/traefik/traefik/v2?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <2.11.42
- Fixed in
- 2.11.42
go get github.com/traefik/traefik/v2@v2.11.42- Affected
- >=3.0.0-beta1 <3.6.12
- Fixed in
- 3.6.12
go get github.com/traefik/traefik/v3@v3.6.12- Affected
- >=3.7.0-ea.1 <3.7.0-ea.3
- Fixed in
- 3.7.0-ea.3
go get github.com/traefik/traefik/v3@v3.7.0-ea.3Details
Summary
There is a potential vulnerability in Traefik's Basic and Digest authentication middlewares when headerField is configured with a non-canonical HTTP header name.
An authenticated attacker with valid credentials can inject the canonical version of the configured header to impersonate any identity to the backend. Because Traefik writes the authenticated username using a non-canonical map key, it creates a separate header entry rather than overwriting the attacker's canonical one — causing most backend frameworks to read the attacker-controlled value instead.
Patches
- <https://github.com/traefik/traefik/releases/tag/v2.11.42>
- <https://github.com/traefik/traefik/releases/tag/v3.6.12>
- <https://github.com/traefik/traefik/releases/tag/v3.7.0-ea.3>
For more information
If there are any questions or comments about this advisory, please open an issue.
---
<details> <summary>Original Description</summary>
Summary
When headerField is configured with a non-canonical HTTP header name (e.g., x-auth-user instead of X-Auth-User), an authenticated attacker can inject a canonical version of that header to impersonate any identity to the backend. The backend receives two header entries — the attacker-injected canonical one is read first, overriding Traefik's non-canonical write.
Tested on Traefik v3.6.10.
Details
At pkg/middlewares/auth/basic_auth.go:92, the authenticated username is written using direct map assignment:
req.Header[b.headerField] = []string{user}Go's http.Header map is keyed by canonical names (e.g., X-Auth-User). Direct assignment with a non-canonical key (x-auth-user) creates a separate map entry from any canonical-key entry already present. The attacker's X-Auth-User: superadmin occupies the canonical slot and is never overwritten by Traefik's non-canonical write.
The same bug exists in pkg/middlewares/auth/digest_auth.go:100. Notably, forward.go:254 correctly uses http.CanonicalHeaderKey(), showing the fix pattern already exists in the codebase.
PoC
Traefik config (YAML, Docker labels, or REST API):
middlewares:
auth:
basicAuth:
users: ["admin:$2y$05$..."]
headerField: "x-auth-user"Normal request (baseline):
curl -u admin:admin http://traefik/secure/test # Backend receives: x-auth-user: admin # Identity = admin ✓
Attack request:
curl -u admin:admin -H "X-Auth-User: superadmin" http://traefik/secure/test # Backend receives BOTH headers: # X-Auth-User: superadmin ← attacker-injected (canonical key, read first by most frameworks) # x-auth-user: admin ← Traefik-set (non-canonical, ignored by most frameworks) # Identity seen by backend = superadmin ✗
Control test — when headerField uses canonical casing (X-Auth-User), the attack fails. Traefik's write correctly overwrites the attacker's header.
This is realistic because YAML conventions favor lowercase keys, Traefik docs don't warn about canonicalization, and the pattern of backends trusting the headerField header is recommended in Traefik's own documentation.
Fix suggestion:
// basic_auth.go:92 and digest_auth.go:100 — change:
req.Header[b.headerField] = []string{user}
// to:
req.Header.Set(b.headerField, user)Also strip any incoming headerField header before the auth check with req.Header.Del(b.headerField).
Impact
An authenticated attacker with valid credentials (even low-privilege) can impersonate any other user identity to backend services. If backends use the headerField header for authorization decisions (which is the intended use case per Traefik docs), this enables privilege escalation — e.g., a regular user impersonating an admin.
The attack requires the operator to configure headerField with a non-canonical header name, which is the natural thing to do in YAML and is not warned against in documentation.
</details>
Is GHSA-qr99-7898-vr7c in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/traefik/traefik/v2, and gives you the command that fixes it.
More advisories for github.com/traefik/traefik/v2
- LowCVE-2026-88012Traefik: respondingTimeouts.readTimeout is not applied to HTTP/3, leaving slow-body uploads unbounded in github.com/traefik/traefik · 16 Sept 2026
- LowCVE-2026-88011Traefik: ForwardAuth identity spoofing via dot-form header alias in github.com/traefik/traefik · 16 Sept 2026
- LowCVE-2026-88009Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging in github.com/traefik/traefik · 16 Sept 2026
- LowCVE-2026-88007Traefik HTTP/3 Backend NTLM Connection Reuse in github.com/traefik/traefik · 16 Sept 2026
- LowCVE-2026-88004Traefik entrypoint header-name sanitization bypassed via request trailers in github.com/traefik/traefik · 16 Sept 2026
- LowCVE-2026-88008Traefik: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') and Incorrect Authorization in github.com/traefik/traefik · 16 Sept 2026
References
- Linkgithub.com/traefik/traefik/security/advisories/GHSA-qr99-7898-vr7c
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-33433
- Linkaccess.redhat.com/errata/RHSA-2026:10175
- Linkaccess.redhat.com/security/cve/CVE-2026-33433
- Linkbugzilla.redhat.com/show_bug.cgi?id=2452289
- Packagegithub.com/traefik/traefik
- Linkgithub.com/traefik/traefik/releases/tag/v2.11.42
- Linkgithub.com/traefik/traefik/releases/tag/v3.6.11
- Linkgithub.com/traefik/traefik/releases/tag/v3.7.0-ea.3
- Linksecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33433.json
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.