CVE-2026-103257: n8n: path traversal in n8n node exposes credentials

HIGH
Published October 1, 2026
CISO Take

n8n, a workflow automation platform widely used to orchestrate AI agents, has a path traversal flaw in its built-in n8n node: resource identifiers are not validated, so an attacker can redirect API calls to unintended endpoints and read workflows, executions and credential secrets within the API key's scope. The CVSS is 7.7 (high), but attack complexity is high and the EPSS score is low (0.00427, around the 65th percentile). It is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK, so this is not an emergency. The real concern is the blast radius: n8n credential stores usually hold LLM provider keys, vector database tokens and SaaS OAuth secrets. Upgrade to 1.123.80, 2.39.6 or 2.40.1 (depending on your branch), and review the scope of any API keys used by the n8n node.

Sources:NVDEPSSGitHub Advisoryvulncheck.comATLAS

What is the risk?

Moderate-high. Impact is high for confidentiality and integrity (C:H/I:H), with limited availability impact. It is network-exploitable with no privileges and no user interaction, but high attack complexity reduces the likelihood. EPSS is low, there is no public exploit and no KEV listing. The exposure is greatest where workflows use the n8n node to manage other n8n instances or where user-controlled data feeds the resource ID field. The CVSS scope is unchanged, but the secrets reachable through the key may unlock many downstream AI services.

How does the attack unfold?

Initial Access
Attacker reaches the n8n API or a workflow that passes user-controlled input as a resource ID to the n8n node.
AML.T0049
Exploitation
A crafted resource ID with path traversal sequences redirects the API call to an unintended resource.
AML.T0049
Credential Access
The attacker reads credential secrets, workflows and executions within the API key's scope.
AML.T0098
Impact
Stolen LLM and SaaS credentials enable downstream access, data exfiltration and tampering with agent workflows.
AML.T0025

What systems are affected?

PackageEcosystemVulnerable RangePatched
n8nnpm—No patch
210.5KOpenSSF 7.116 dependentsPushed 3d ago42% patched~19d to patchFull package profile →

Do you use n8n? You're affected.

How severe is it?

CVSS 3.1
7.7 / 10
EPSS
0.4%
chance of exploitation in 30 days
Higher than 38% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Moderate

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACHigh
PRNone
UINone
SUnchanged
CHigh
IHigh
ALow

What should I do?

1 step
  1. 1) Patch to 1.123.80, 2.39.6 or 2.40.1 or later, depending on your branch. 2) Rotate API keys used by the n8n node, and rotate any credentials stored in the affected instance if exposure is suspected. 3) Restrict API key scopes to least privilege and limit network access to the n8n API. 4) Do not pass untrusted or user-controlled input into resource ID parameters of the n8n node. 5) Detection: monitor n8n API logs for resource identifiers containing path sequences such as '../' or encoded variants (%2e%2e), and for unexpected reads of credentials, workflows or executions.

What does CISA's SSVC say?

DecisionTrack
Exploitationnone
AutomatableNo
Technical Impacttotal

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Art. 15-Accuracy, robustness and cybersecurity
ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
MANAGE 2.3-Responses to previously unknown risks
OWASP LLM Top 10
LLM06-Excessive Agency

Frequently Asked Questions

What is CVE-2026-103257?

n8n, a workflow automation platform widely used to orchestrate AI agents, has a path traversal flaw in its built-in n8n node: resource identifiers are not validated, so an attacker can redirect API calls to unintended endpoints and read workflows, executions and credential secrets within the API key's scope. The CVSS is 7.7 (high), but attack complexity is high and the EPSS score is low (0.00427, around the 65th percentile). It is not in CISA KEV, no public exploit or Nuclei template exists, and CISA SSVC says TRACK, so this is not an emergency. The real concern is the blast radius: n8n credential stores usually hold LLM provider keys, vector database tokens and SaaS OAuth secrets. Upgrade to 1.123.80, 2.39.6 or 2.40.1 (depending on your branch), and review the scope of any API keys used by the n8n node.

Is CVE-2026-103257 actively exploited?

No confirmed active exploitation of CVE-2026-103257 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-103257?

1) Patch to 1.123.80, 2.39.6 or 2.40.1 or later, depending on your branch. 2) Rotate API keys used by the n8n node, and rotate any credentials stored in the affected instance if exposure is suspected. 3) Restrict API key scopes to least privilege and limit network access to the n8n API. 4) Do not pass untrusted or user-controlled input into resource ID parameters of the n8n node. 5) Detection: monitor n8n API logs for resource identifiers containing path sequences such as '../' or encoded variants (%2e%2e), and for unexpected reads of credentials, workflows or executions.

What systems are affected by CVE-2026-103257?

This vulnerability affects the following AI/ML architecture patterns: agent frameworks, workflow automation, RAG pipelines, LLM orchestration.

What is the CVSS score for CVE-2026-103257?

CVE-2026-103257 has a CVSS v3.1 base score of 7.7 (HIGH). The EPSS exploitation probability is 0.43%.

What is the AI security impact?

Affected AI Architectures

agent frameworksworkflow automationRAG pipelinesLLM orchestration

MITRE ATLAS Techniques

AML.T0049Exploit Public-Facing Application
AML.T0083Credentials from AI Agent Configuration
AML.T0098AI Agent Tool Credential Harvesting

Compliance Controls Affected

EU AI Act: Art. 15
ISO 42001: A.6.2.6
NIST AI RMF: MANAGE 2.3
OWASP LLM Top 10: LLM06

What are the technical details?

Original Advisory

n8n versions before 1.123.80, from 2.0.0 before 2.39.6, and from 2.40.0 before 2.40.1 contain a path traversal vulnerability in the n8n node that fails to validate resource identifiers. Attackers can craft malicious resource IDs to redirect API calls to unintended resources, allowing unauthorized access to workflows, executions, and credential secrets within the API key's scope.

Exploitation Scenario

An attacker finds a workflow, exposed via a webhook or a chat-driven AI agent, that passes user-supplied input as a resource ID to the n8n node. They send a crafted ID containing path traversal sequences, which redirects the internal API call to a different endpoint, such as credentials or executions. The response returns secrets within the API key's scope, including LLM provider keys and vector database tokens. With these they access downstream AI services, exfiltrate execution data or alter workflows to establish persistence.

Weaknesses (CWE)

CWE-22 — Improper Limitation of a Pathname to a Restricted Directory: The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

  • [Implementation] Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylis
  • [Architecture and Design] For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L

Timeline

Published
October 1, 2026
Last Modified
October 1, 2026
First Seen
October 1, 2026

Related Vulnerabilities