Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.9, published 22 July 2026.
- Which products and versions are affected?
- N8n < 1.123.64, 2.29.8, 2.30.1.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a network appliance.
- Am I affected?
- Check whether you run N8n at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Time-of-Check Time-of-Use (TOCTOU) race condition exists in the Git node's clone operation in n8n. An authenticated attacker can bypass path restrictions by replacing a validated directory with a symbolic link before the clone operation executes. By redirecting the clone to the community node directory, the attacker can plant a malicious repository that n8n loads as a custom node upon the next restart. This results in arbitrary JavaScript execution in the context of the n8n server. The vulnerability affects both self-hosted and cloud instances and is addressed in versions 1.123.64, 2.29.8, and 2.30.1.
Affected products
- n8n n8n < 1.123.64, 2.29.8, 2.30.1
Timeline
- 2026-07-22: advisory: Original advisory published and subsequently withdrawn as a duplicate.