Traefik is an HTTP reverse proxy and load balancer. Prior to v2.11.51, v3.6.22, and v3.7.6, Traefik's ForwardAuth middleware, even when configured with trustForwardHeader: false, derives the X-Forwarded-Port header sent to the authentication service from the original incoming request instead of the sanitized forwarded request. As a result, an unauthenticated remote attacker can inject an X-Forwarded-Proto: https header over a plain HTTP connection and cause Traefik to forward X-Forwarded-Port: 443 to the authentication service, bypassing port-based authorization checks. This issue is fixed in versions v2.11.51, v3.6.22, and v3.7.6.
CVE-2026-54764
This medium-severity CVE scores 5.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.8
- EG Score
- 5.8(medium)
- EPSS
- 20.9%
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 8, 2026
Advisory Details (3)
Auto-updated Jul 7, 2026ForwardAuth middleware leaks X-Forwarded-Port spoofing via untrusted X-Forwarded-Proto when trustForwardHeader=false · Advisory · traefik/traefik · GitHub
https://github.com/traefik/traefik/security/advisories/GHSA-3q9r-p662-5j8mFix x-forwarded-port in forward-auth
Fix merged in traefik/traefik PR #13344 on 2026-06-11 — awaiting tagged release
https://github.com/traefik/traefik/pull/13344commit 7ae92d8c2c10 (traefik/traefik)
Fix landed in traefik/traefik commit 7ae92d8c2c10 — awaiting tagged release
https://github.com/traefik/traefik/commit/7ae92d8c2c10ac04ef5a03df0ed5019ce0f44b2dWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 17:04 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 17:45 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 18:26 UTCEG score recompute
- 2026-07-08 19:07 UTCEG score recompute▼ 1.10
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 04:32 UTCNVD updateCVSS v3 → 5.8
- 2026-07-07 19:49 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 20:30 UTCEG score recompute
- 2026-07-06 20:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-345
Frequently asked(5)
What is CVE-2026-54764?
When was CVE-2026-54764 disclosed?
Is CVE-2026-54764 actively exploited?
What is the CVSS score of CVE-2026-54764?
How do I remediate CVE-2026-54764?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54764
Is Your Infrastructure Affected by CVE-2026-54764?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.