Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-65598: n8n before 1.123.64, 2.29.8, and 2.30.1 contains a TOCTOU race condition in the Git node's clone operation tha

33
Routine
HIGH 7.5UPGRADE

CVE-2026-65598 is a high-severity flaw (CVSS 7.5) affecting n8n. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 sel

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededLow
User interactionNone
EPSS exploit chance0.3% (top 74%)
CISA exploited listNo
WeaknessCWE-367
Published2026-07-22
Last modified2026-10-24
Publisher (CNA): VulnCheck · Vendor: n8n

Share: LinkedIn · X · Reddit

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

n8n n8n UPGRADE
Affected: < 1.123.64 · >= 2.0.0 and < 2.29.8 · 2.30.0
Fixed in: 1.123.64, 2.29.8
Safe to downgrade to: a release before 2.0.0
1. Check installed version
npm ls n8n
2. UPGRADE to 1.123.64
npm install n8n@">=1.123.64"
3. If no update is available yet, DOWNGRADE to a release before 2.0.0
npm view n8n versions npm install n8n@"<2.0.0"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Exact fixes by distribution

npm · n8n · FIXED · 1.123.64 · vulnerable: < 1.123.64 · source
npm install n8n@">=1.123.64" npm ls n8n
Fedora 46 · newscache · FIXED · 1.3.22-1.fc46 · FEDORA-2026-49b088f8ca · source
sudo dnf upgrade --advisory=FEDORA-2026-49b088f8ca
Fedora ELN · selinux-policy · FIXED · 45.23-1.eln159 · FEDORA-2026-3668c969a2 · source
sudo dnf upgrade --advisory=FEDORA-2026-3668c969a2
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-65598?

n8n: upgrade to 1.123.64, 2.29.8. Exact commands for each OS are on this page.

Is CVE-2026-65598 being exploited?

CVE-2026-65598 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-65598 affect?

CVE-2026-65598 affects n8n. Severity is high (CVSS 7.5). 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 bef

How urgent is CVE-2026-65598?

Priority 33/100. High severity

Software pages

Git vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.