Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-33433

github.com/traefik/traefik: Traefik: Authentication bypass via non-canonical HTTP header injection

Overview

Published
27 Mar 2026
Modified
15 Jul 2026
Medium CVE
2 Registry packages
4 OS packages
2 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

8.8 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-290

Affected packages · 2

Packages affected by CVE-2026-33433
EcosystemPackageVulnerableFixed in
Go github.com/traefik/traefik/v2 <2.11.42 2.11.42
Go github.com/traefik/traefik/v3 >=3.0.0-beta1, <3.6.12>=3.7.0-ea.1, <3.7.0-ea.3 3.6.123.7.0-ea.3

Open a package to see all its vulnerabilities.

Operating systems · 2 fixes

chainguard 1 release · 1 package

fixed 1
traefik-2-11
chainguard fixes for CVE-2026-33433
ReleasePackageFixed in
traefik-2-11 +1 2.11.42-r0

minimos 1 release · 1 package

fixed 1
traefik-3
minimos fixes for CVE-2026-33433
ReleasePackageFixed in
traefik-3 +1 3.6.11-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.