Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik used the backend Service namespace instead of the HTTPRoute namespace. A low-privileged route author holding a ReferenceGrant for a cross-namespace Service could therefore bind a Traefik Middleware from the backend namespace without a separate grant for that middleware, potentially injecting trusted reverse-proxy identity headers into downstream requests. The issue is fixed in version 3.7.7.
CVE-2026-65601
MEDIUMPre-NVD 5.35.3Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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).
Triggered by: NVD CVSS baseline
Sources: secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 5.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EPSS
- —
- KEV
- Not listed
Published
July 22, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Jul 22, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit.
generic Patch Available
Traefik before 3.7.7 Namespace Confusion via HTTPRoute ExtensionRef | Advisories | VulnCheck
https://www.vulncheck.com/advisories/traefik-before-namespace-confusion-via-httproute-extensionrefgithub_commit
commit 26c96a3935ca (traefik/traefik)
Fix landed in traefik/traefik commit 26c96a3935ca — awaiting tagged release
https://github.com/traefik/traefik/commit/26c96a3935cafb473f4a5bae1886560d9aa4e4f0github Patch Available🟡 PoC Available
Traefik Gateway API HTTPRoute BackendRef ExtensionRef Namespace Confusion · Advisory · traefik/traefik · GitHub
https://github.com/traefik/traefik/security/advisories/GHSA-qq9q-x9w4-chhjVendor Advisories for CVE-2026-65601(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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-22 13:35 UTCEG score recompute
- 2026-07-22 13:35 UTCGHSA enrichment
- 2026-07-22 11:32 UTCEG score recompute
- 2026-07-22 11:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(4)
What is CVE-2026-65601?
CVE-2026-65601 is a medium vulnerability published on July 22, 2026. Traefik versions 3.7.0 through 3.7.6 contain a namespace confusion vulnerability in the Kubernetes Gateway API provider. When resolving HTTPRoute.spec.rules[].backendRefs[].filters[].extensionRef, Traefik used the backend Service namespace instead of the HTTPRoute namespace. A low-privileged route…
When was CVE-2026-65601 disclosed?
CVE-2026-65601 was first published in the National Vulnerability Database on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-65601?
CVE-2026-65601 has a CVSS v3 base score of 5.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-65601?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65601, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65601
Is Your Infrastructure Affected by CVE-2026-65601?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.