CVE-2026-65598

HIGHPre-NVD 8.98.9
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.9 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
Trending — 3 sources updated this week
8.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

n8n before 1.123.64, 2.29.8, and 2.30.1 contains a TOCTOU race condition in the Git node's clone operation that allows authenticated users to bypass path restrictions by swapping a directory for a symlink after the path is validated but before the clone runs. This lets an attacker plant a crafted repository in the community node directory, which n8n loads as a custom node on the next restart, executing arbitrary JavaScript on the server. Both self-hosted and cloud instances are affected.

CVSS v3
8.9
EG Score
8.9(low)
EPSS
—
KEV
Not listed

Published

July 22, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
Patch available. Sources: github.
generic

n8n before 1.123.64 Remote Code Execution via Git Clone | Advisories | VulnCheck

https://www.vulncheck.com/advisories/n8n-before-remote-code-execution-via-git-clone
github Patch Available

Race Condition in Git Clone Node Allows Authenticated Users to Achieve Remote Code Execution · Advisory · n8n-io/n8n · GitHub

https://github.com/n8n-io/n8n/security/advisories/GHSA-g3r5-9h93-4j2c

Vendor Advisories for CVE-2026-65598(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 33× in last 7d / 33× 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.

  1. 2026-07-22 17:20 UTCGHSA enrichment
  2. 2026-07-22 13:35 UTCEG score recompute
  3. 2026-07-22 13:35 UTCGHSA enrichment
  4. 2026-07-22 13:33 UTCGHSA enrichment
  5. 2026-07-22 13:31 UTCGHSA enrichment
  6. 2026-07-22 13:29 UTCGHSA enrichment
  7. 2026-07-22 13:28 UTCGHSA enrichment
  8. 2026-07-22 13:26 UTCGHSA enrichment
  9. 2026-07-22 13:26 UTCGHSA enrichment
  10. 2026-07-22 13:24 UTCGHSA enrichment
  11. 2026-07-22 13:23 UTCGHSA enrichment
  12. 2026-07-22 13:22 UTCGHSA enrichment
  13. 2026-07-22 13:21 UTCGHSA enrichment
  14. 2026-07-22 13:17 UTCGHSA enrichment
  15. 2026-07-22 13:15 UTCGHSA enrichment
  16. 2026-07-22 13:14 UTCGHSA enrichment
  17. 2026-07-22 13:14 UTCGHSA enrichment
  18. 2026-07-22 13:09 UTCGHSA enrichment
  19. 2026-07-22 13:08 UTCGHSA enrichment
  20. 2026-07-22 13:02 UTCGHSA enrichment
  21. 2026-07-22 13:00 UTCGHSA enrichment
  22. 2026-07-22 12:59 UTCGHSA enrichment
  23. 2026-07-22 12:59 UTCGHSA enrichment
  24. 2026-07-22 12:57 UTCGHSA enrichment
  25. 2026-07-22 12:56 UTCGHSA enrichment
Show 8 more
  1. 2026-07-22 12:55 UTCGHSA enrichment
  2. 2026-07-22 12:54 UTCGHSA enrichment
  3. 2026-07-22 12:53 UTCGHSA enrichment
  4. 2026-07-22 12:51 UTCGHSA enrichment
  5. 2026-07-22 12:50 UTCGHSA enrichment
  6. 2026-07-22 12:49 UTCGHSA enrichment
  7. 2026-07-22 11:32 UTCEG score recompute
  8. 2026-07-22 11:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-65598?
CVE-2026-65598 is a high vulnerability published on July 22, 2026. n8n before 1.123.64, 2.29.8, and 2.30.1 contains a TOCTOU race condition in the Git node's clone operation that allows authenticated users to bypass path restrictions by swapping a directory for a symlink after the path is validated but before the clone runs. This lets an attacker plant a crafted…
When was CVE-2026-65598 disclosed?
CVE-2026-65598 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-65598?
CVE-2026-65598 has a CVSS v3 base score of 8.9 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-65598?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65598, 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-65598

Explore →

Is Your Infrastructure Affected by CVE-2026-65598?

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

Start Free Scan →Browse All CVEs