Is there a patch available for CVE-2026-56352?

Yes, a patch is available for CVE-2026-56352. Update the affected software to the latest version immediately.

n8n CVE-2026-56352

Q: What is the CVSS score of CVE-2026-56352?

CVE-2026-56352 has a CVSS 4.0 base score of 5.3 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-44625 MEDIUM

Path Traversal (CWE-22)

2026-07-15 VulnCheck

GHSA-w243-4jxf-88rr

Path Traversal N8n

5.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

5.3 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.4 MEDIUM

Network REST API access with low-privilege authenticated user; scope changes to downstream connected systems justify S:C; confidentiality and integrity impacts are limited to file disclosure and workflow execution respectively.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Jul 15, 2026 - 13:03 EUVD

Source Code Evidence Fetched

Jul 15, 2026 - 12:38 vuln.today

Analysis Generated

Jul 15, 2026 - 12:38 vuln.today

DescriptionCVE.org

n8n before 2.19.3 contains a file path restriction bypass in the legacy ExecuteWorkflow node's localFile source option, which reads workflow files from disk without the file-access checks enforced by other file-reading nodes. Although hidden from the UI since v1.2, it remains reachable via the REST API. An authenticated user with permission to create or modify workflows can supply an arbitrary file path to bypass the N8N_RESTRICT_FILE_ACCESS_TO restriction and determine whether arbitrary files exist on the host; where the targeted path contains a valid workflow JSON file, that file can additionally be loaded and executed.

AnalysisAI

File path restriction bypass in n8n before 2.19.3 allows authenticated users with workflow creation or modification rights to circumvent the N8N_RESTRICT_FILE_ACCESS_TO security boundary via a legacy REST API code path, enabling arbitrary file existence disclosure on the host filesystem. Where a targeted path contains valid workflow JSON, that file can additionally be loaded and executed by the n8n engine, potentially triggering downstream actions on all systems connected to that workflow. No public exploit or active exploitation has been identified at time of analysis, but the low complexity and broad impact on connected downstream systems make this a meaningful risk in multi-tenant or partially-trusted deployments.

Technical ContextAI

n8n is an open-source workflow automation platform distributed as the npm package 'n8n', affected across all versions captured by CPE cpe:2.3:a:n8n:n8n:*:*:*:*:*:*:*:* prior to 2.19.3. The vulnerable code path is the ExecuteWorkflow node's 'localFile' source option, which reads workflow definition files directly from disk. Unlike other file-reading nodes in n8n that enforce the N8N_RESTRICT_FILE_ACCESS_TO environment variable to sandbox permitted filesystem paths, this legacy option omits those checks entirely. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, 'Path Traversal'): attacker-controlled file paths are accepted and resolved without canonicalization or directory boundary enforcement. Although this option was removed from the n8n UI in version 1.2, the underlying REST API endpoint was not disabled, leaving the code path reachable by any client that can construct a raw API request.

RemediationAI

The primary remediation is to upgrade n8n to version 2.19.3 or 2.20.0 (or any later release), as confirmed by the vendor in GHSA-2vx9-7wpg-88jq (https://github.com/n8n-io/n8n/security/advisories/GHSA-2vx9-7wpg-88jq). If an immediate upgrade is not feasible, the vendor identifies two temporary mitigations, both explicitly noted as incomplete: first, restrict workflow creation and editing permissions to fully trusted administrators only - this requires auditing all existing user grants and prevents untrusted insiders from exploiting the REST API path, but does not close the underlying code path; second, restrict network access to the n8n REST API via firewall rules, API gateway controls, or network segmentation to trusted hosts only - this reduces external exposure but does not protect against insider threats or already-compromised accounts. Neither workaround eliminates the vulnerable code path; both are short-term measures pending upgrade.