CVE-2026-65601

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% 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).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

July 22, 2026

Last Modified

August 6, 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-extensionref
github_commit

commit 26c96a3935ca (traefik/traefik)

Fix landed in traefik/traefik commit 26c96a3935ca — awaiting tagged release

https://github.com/traefik/traefik/commit/26c96a3935cafb473f4a5bae1886560d9aa4e4f0
github 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-chhj

Vendor Advisories for CVE-2026-65601(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdevspaces/traefik-rhel9:17877567992026-09-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/traefik/traefik———
Traefik—3.7.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 63× 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.

Showing the most recent 100 of 178 total refreshes for this CVE.

  1. 2026-09-18 22:42 UTCEG score recompute
  2. 2026-09-18 22:42 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 03:11 UTCEG score recompute
  5. 2026-09-18 03:11 UTCVendor advisory
  6. 2026-09-17 02:13 UTCEG score recompute
  7. 2026-09-17 02:13 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 07:05 UTCEG score recompute
  10. 2026-09-16 07:05 UTCVendor advisory
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-14 10:17 UTCVendor advisory
  13. 2026-09-13 22:26 UTCEG score recompute
  14. 2026-09-13 22:26 UTCVendor advisory
  15. 2026-09-13 08:28 UTCVendor advisory
  16. 2026-09-12 20:54 UTCEG score recompute
  17. 2026-09-12 20:54 UTCVendor advisory
  18. 2026-09-12 09:16 UTCVendor advisory
  19. 2026-09-11 20:56 UTCEG score recompute
  20. 2026-09-11 20:56 UTCVendor advisory
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 09:37 UTCEPSS rescore
  23. 2026-09-11 09:15 UTCVendor advisory
  24. 2026-09-10 21:40 UTCEG score recompute
  25. 2026-09-10 21:40 UTCVendor advisory
Show 75 more
  1. 2026-09-09 09:18 UTCEG score recompute
  2. 2026-09-09 09:18 UTCVendor advisory
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 21:43 UTCEG score recompute
  5. 2026-09-07 21:43 UTCVendor advisory
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 08:45 UTCVendor advisory
  9. 2026-09-05 19:35 UTCEG score recompute
  10. 2026-09-05 19:35 UTCVendor advisory
  11. 2026-09-05 15:31 UTCEPSS rescore
  12. 2026-09-05 07:16 UTCEG score recompute
  13. 2026-09-05 07:16 UTCVendor advisory
  14. 2026-09-04 13:58 UTCEG score recompute
  15. 2026-09-04 13:58 UTCVendor advisory
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 23:41 UTCEG score recompute
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-08-31 00:09 UTCEG score recompute
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 12:35 UTCEG score recompute
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-30 00:56 UTCEG score recompute
  26. 2026-08-28 21:42 UTCEPSS rescore
  27. 2026-08-27 21:54 UTCEG score recompute
  28. 2026-08-26 19:58 UTCEG score recompute
  29. 2026-08-26 14:47 UTCEPSS rescore
  30. 2026-08-25 17:49 UTCEG score recompute
  31. 2026-08-25 13:49 UTCEPSS rescore
  32. 2026-08-24 18:15 UTCEG score recompute
  33. 2026-08-23 05:48 UTCEG score recompute
  34. 2026-08-23 00:19 UTCEPSS rescore
  35. 2026-08-22 06:39 UTCEG score recompute
  36. 2026-08-21 23:49 UTCEPSS rescore
  37. 2026-08-21 07:31 UTCEG score recompute
  38. 2026-08-20 22:56 UTCEPSS rescore
  39. 2026-08-19 20:45 UTCEG score recompute
  40. 2026-08-19 17:04 UTCEPSS rescore
  41. 2026-08-18 20:29 UTCEG score recompute
  42. 2026-08-18 13:48 UTCEPSS rescore
  43. 2026-08-17 20:28 UTCEG score recompute
  44. 2026-08-17 13:47 UTCEPSS rescore
  45. 2026-08-16 19:09 UTCEG score recompute
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 07:19 UTCEG score recompute
  48. 2026-08-15 08:11 UTCEG score recompute
  49. 2026-08-15 01:30 UTCEPSS rescore
  50. 2026-08-14 09:02 UTCEG score recompute
  51. 2026-08-13 22:00 UTCEPSS rescore
  52. 2026-08-12 22:20 UTCEG score recompute
  53. 2026-08-12 13:51 UTCEPSS rescore
  54. 2026-08-11 23:11 UTCEG score recompute
  55. 2026-08-11 00:03 UTCEG score recompute
  56. 2026-08-11 00:00 UTCEPSS rescore
  57. 2026-08-10 00:46 UTCEG score recompute
  58. 2026-08-09 13:47 UTCEPSS rescore
  59. 2026-08-09 01:38 UTCEG score recompute
  60. 2026-08-08 16:37 UTCEPSS rescore
  61. 2026-08-08 02:29 UTCEG score recompute
  62. 2026-08-06 15:47 UTCEG score recompute▲ 3.50
  63. 2026-08-06 15:47 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  64. 2026-08-06 13:47 UTCEPSS rescore
  65. 2026-08-05 22:20 UTCEG score recompute
  66. 2026-08-05 19:17 UTCEPSS rescore
  67. 2026-08-05 19:17 UTCEPSS rescore
  68. 2026-08-04 22:50 UTCEG score recompute
  69. 2026-08-04 22:50 UTCGHSA enrichment
  70. 2026-08-04 15:10 UTCEPSS rescore
  71. 2026-08-04 10:39 UTCEPSS rescore
  72. 2026-08-03 23:18 UTCEG score recompute
  73. 2026-08-03 23:18 UTCGHSA enrichment
  74. 2026-08-03 10:36 UTCEPSS rescore
  75. 2026-08-02 23:47 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-65601?
CVE-2026-65601 is a high 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, with the most recent update on August 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65601 actively exploited?
CVE-2026-65601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.2% of all scored CVEs.
What is the CVSS score of CVE-2026-65601?
CVE-2026-65601 has a CVSS v3 base score of 8.8 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65601

Explore →

Is Your Infrastructure Affected by CVE-2026-65601?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs