CVE-2026-71539
Received Received - Intake

Symlink Attack in n8n Workflow Automation Platform

Vulnerability report for CVE-2026-71539, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-18

Last updated on: 2026-08-18

Assigner: GitHub, Inc.

Description

n8n is an open source workflow automation platform. Prior to 1.123.64, 2.29.8, and 2.30.1, the Git node clone operation allows an authenticated workflow user to swap a validated directory for a symlink before cloning, planting a crafted repository in the community node directory that loads as a custom JavaScript node after restart and executes arbitrary code on the server. This issue is fixed in versions 1.123.64, 2.29.8, and 2.30.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-18
Last Modified
2026-08-18
Generated
2026-08-18
AI Q&A
2026-08-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
n8n-io n8n to 1.123.64 (exc)
n8n-io n8n to 2.29.8 (exc)
n8n-io n8n to 2.30.1 (exc)
n8n n8n to 1.123.64 (inc)
n8n n8n to 2.29.8 (inc)
n8n n8n to 2.30.1 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-367 The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a race condition in the Git clone node of n8n versions before 1.123.64, 2.29.8, and 2.30.1. An authenticated user can replace a validated directory with a symlink before the clone operation completes, planting a malicious repository in the community node directory. On restart, n8n loads this as a custom JavaScript node, allowing arbitrary code execution on the server.

Detection Guidance

Detecting this vulnerability requires checking n8n versions and monitoring for suspicious Git node usage. Verify installed versions against patched releases (1.123.64, 2.29.8, 2.30.1). Inspect workflows using the Git node for unusual repository paths or symlink patterns. Monitor server logs for unexpected JavaScript node loads or code execution events.

Impact Analysis

This vulnerability allows an authenticated attacker to execute arbitrary code on the server running n8n. It can lead to full system compromise, data theft, or disruption of services. Both self-hosted and cloud instances are affected if authenticated users can create and run workflows using the Git node.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR and HIPAA requirements for data protection and confidentiality. A successful exploit may result in data breaches, triggering compliance violations and potential legal penalties.

Mitigation Strategies

Immediately upgrade n8n to versions 1.123.64, 2.29.8, or 2.30.1 or later. Restrict instance access to trusted users only. Disable the Git node via the NODES_EXCLUDE environment variable. Limit network egress to prevent connections to untrusted repositories. Review and audit all workflows using the Git node for signs of exploitation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-71539. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart