{"answers":{"affected":"2 open source packages ship an affected version, including n8n.","exploited":"There is no known exploitation of CVE-2026-56352 in the wild and no public exploit code.","fix":"Upgrade n8n to 2.19.3 or later.","what":"CVE-2026-56352 is a medium-severity path traversal vulnerability in n8n, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56352 and fix it if it is affected.\n\nWhat it is: CVE-2026-56352 is a medium-severity path traversal vulnerability in n8n, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56352 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- n8n (npm): affected all versions; fixed in 2.19.3\n- n8n (npm): affected all versions; fixed in 2.19.3\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-56352/ (Markdown: https://insights.sbomify.com/CVE-2026-56352/index.md)","id":"CVE-2026-56352","markdown":"https://insights.sbomify.com/CVE-2026-56352/index.md","name":"CVE-2026-56352","record":{"aliases":["GHSA-2vx9-7wpg-88jq","GHSA-w243-4jxf-88rr","ROOT-APP-NPM-GHSA-2vx9-7wpg-88jq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"n8n workflow automation","requires_auth":"low_privilege","summary":"Authenticated users can bypass file access restrictions to read arbitrary files and execute workflow JSON files via the ExecuteWorkflow node.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"n8n - Arbitrary File Read and Execution via ExecuteWorkflow localFile Parameter","id":"CVE-2026-56352","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"n8n - Authentication Bypass in Chat Trigger Node","id":"CVE-2026-56353"},"packages":[{"ecosystem":"npm","fixed":["2.19.3"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":null,"source":"GHSA-2vx9-7wpg-88jq"},{"ecosystem":"npm","fixed":["2.19.3"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":"pkg:npm/n8n","source":"GHSA-2vx9-7wpg-88jq"}],"prev":{"headline":"n8n - SQL Injection in MySQL, PostgreSQL, and Microsoft SQL Nodes","id":"CVE-2026-56351"},"products":["n8n"],"published":"2026-07-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["n8n"]},"summary":"Authenticated users can bypass file access restrictions to read arbitrary files and execute workflow JSON files via the ExecuteWorkflow node.","url":"https://insights.sbomify.com/CVE-2026-56352/"}