# CVE-2026-103257: n8n before 1.123.80, 2.39.6, and 2.40.1 Path Traversal via n8n Node

> Attackers can exploit path traversal in n8n nodes to access unauthorized workflows, executions, and credential secrets via crafted resource IDs.

- **Severity:** High 8.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-89p4-6h98-c7xm, GHSA-cfpw-gmwr-v9wc, MINI-wx4r-4g3m-56vx

## What is CVE-2026-103257?

CVE-2026-103257 is a high-severity path traversal vulnerability in n8n-io n8n, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-103257?


## How do I fix CVE-2026-103257?

Upgrade to a fixed version.

## Is CVE-2026-103257 being exploited?

There is no known exploitation of CVE-2026-103257 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103257 and fix it if it is affected.

What it is: CVE-2026-103257 is a high-severity path traversal vulnerability in n8n-io n8n, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103257 in the wild and no public exploit code.

Affected product: n8n-io n8n. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103257/ (Markdown: https://insights.sbomify.com/CVE-2026-103257/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103257
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103257
- OSV: https://osv.dev/vulnerability/CVE-2026-103257

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103257/
Summaries are generated and may contain mistakes; the official description above is the record.