CVE-2026-35051·Traefik vulnerability
Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is an authentication bypass vulnerability in Traefik's ForwardAuth middleware when trustForwardHeader=false is configured and Traefik is deployed behind a trusted upstream proxy. This issue has been patched in versions 2.11.43, 3.6.14, and 3.7.0-rc.2.
- Severity
- critical
- Software
- Traefik
- Fixed in
- 3.6.14
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.31% — higher than 23% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-35051 scores 10 on CVSS, so a successful attack would be serious — but at 0.31%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 3.0.0
Until: 3.6.14
Fixed in: 3.6.14
How to fix this CVE
Upgrade Traefik to version 3.6.14 or later to patch the ForwardAuth middleware authentication bypass. If you are running version 3.0.0 through 3.6.13, immediate patching is critical as this vulnerability allows attackers to bypass authentication when ForwardAuth is misconfigured behind a trusted upstream proxy. Users on older 2.x branches should update to 2.11.43 or migrate to version 3.6.14+.
sudo dnf update traefik-3.6.14Defensia detects this vulnerability
How to check if you are affected
- Step 1: Check installed Traefik version with `traefik version` or inspect the container image tag if running in Docker
- Step 2: Verify ForwardAuth middleware configuration in your static config file (typically /etc/traefik/traefik.yml or docker-compose.yml) and check if `trustForwardHeader: false` is set
- Step 3: Search access logs for unusual authentication header patterns or repeated 401/403 responses followed by successful 200 responses without proper credential re-submission
- Step 4: After upgrading, confirm the new version with `traefik version` and restart the service using `sudo systemctl restart traefik` or redeploy your container
FAQ
What is CVE-2026-35051?
This is a critical authentication bypass in Traefik's ForwardAuth middleware that occurs when trustForwardHeader is disabled and Traefik sits behind a trusted upstream proxy, allowing attackers to forge authentication headers and gain unauthorized access.
Is CVE-2026-35051 being actively exploited?
No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploit code is currently available, though the critical CVSS score warrants immediate patching.
What versions of Traefik are affected by CVE-2026-35051?
Traefik versions 3.0.0 through 3.6.13 are vulnerable. Version 2.x releases prior to 2.11.43 are also affected. Version 3.6.14 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-35051?
Run `traefik version` to retrieve the installed version number. If it is between 3.0.0 and 3.6.13 (inclusive), your deployment is vulnerable and requires immediate updating.
Does Defensia detect CVE-2026-35051?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Traefik is installed on a monitored server, CVE-2026-35051 will appear in your dashboard with remediation steps.
Related Traefik CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-35051. Free for 1 server.
Get started free