CVE-2026-33433: Traefik Vulnerable to BasicAuth/DigestAuth Identity Spoofing via Non-Canonical headerField
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.42, 3.6.11, and 3.7.0-ea.3, 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 their own 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. Versions 2.11.42, 3.6.11, and 3.7.0-ea.3 patch the issue.
Security readout for executives and security teams
Plain-English summary
CVE-2026-33433 lets an authenticated attacker spoof the user identity Traefik forwards to backend services, but only under a specific configuration. If BasicAuth or DigestAuth uses a non-canonical headerField, a backend may trust the attacker-controlled identity header first. Patched Traefik versions are available.
Executive priority
Prioritize this for internet-facing or shared Traefik environments where backend apps trust Traefik-provided identity headers. The issue is high severity but configuration-dependent, so rapid inventory and targeted patching are appropriate.
Technical view
Affected Traefik versions mishandle BasicAuth/DigestAuth headerField when the configured header name is non-canonical. A canonical duplicate header supplied by an authenticated attacker can be processed before Traefik's written header, causing backend identity confusion. CVSS is 7.7 high with high confidentiality and integrity impact.
Likely exposure
Likely exposure is Traefik deployments before 2.11.42, 3.6.11, or 3.7.0-ea.3 that use BasicAuth or DigestAuth with headerField configured using non-canonical casing. Risk is highest where backend applications trust that forwarded identity header for authorization or audit decisions.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Exploitation is conditional: the attacker must be authenticated and the vulnerable headerField configuration must exist. If present, impact can include impersonation and backend authorization bypass.
Researcher notes
Focus analysis on header canonicalization and duplicate-header handling between Traefik middleware and backend frameworks. Evidence supports identity spoofing only when headerField is non-canonical; do not generalize this to all Traefik authentication deployments.
Mitigation direction
Upgrade Traefik to 2.11.42, 3.6.11, 3.7.0-ea.3, or later.
Review Red Hat advisory RHSA-2026:10175 for distribution package status.
Check vendor guidance before relying on compensating controls.
Temporarily reduce trust in forwarded identity headers until patched.
Validation and detection
Inventory Traefik versions and compare them with affected ranges.
Review BasicAuth and DigestAuth configurations for headerField usage.
Identify backend services that trust forwarded identity headers.
Confirm remediation by verifying Traefik runs a patched version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-290 · source CWE mapping
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.