traefik · Traefik · published 2026-03-27
CVE-2026-33433Traefik Vulnerable to BasicAuth/DigestAuth Identity Spoofing via Non-Canonical headerField
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-33433 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 43% of all CVEs. This Traefik vulnerability: CVSS 5.1 (v4.0). Fixed upstream in Traefik 3.7.0-ea.3, 3.7.0-ea.2, 3.6.12, 3.6.11 (+1 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Traefik 3.7.0-ea.3, 3.7.0-ea.2, 3.6.12, 3.6.11, 2.11.42.
Patch events
Web serverTraefik
Traefik security releases: 3.7.0-ea.3, 3.7.0-ea.2, 3.6.12, 3.6.11, 2.11.42
Upgrade to
3.7.0-ea.33.7.0-ea.23.6.123.6.112.11.42Why: CVE-2026-33186: Critical (CVSS 9.1) automatable flaw in an edge product.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (44th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.1 (v4.0)CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- traefik traefik
< 2.11.42(affected)>= 3.0.0-beta1, < 3.6.11(affected)>= 3.7.0-ea.1, < 3.7.0-ea.3(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.