{"answers":{"affected":"4 open source packages ship an affected version, including n8n. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-54311 in the wild and no public exploit code.","fix":"Upgrade n8n to a fixed version for your release line: 2.25.7 or 2.26.2.","what":"CVE-2026-54311 is a medium-severity vulnerability in N8n N8n, published on 23 Jun 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-54311 and fix it if it is affected.\n\nWhat it is: CVE-2026-54311 is a medium-severity vulnerability in N8n N8n, published on 23 Jun 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-54311 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- n8n (npm): affected all versions; fixed in 2.25.7\n- n8n (npm): affected all versions; fixed in 2.25.7\n- n8n (npm): affected from 2.26.0; fixed in 2.26.2\n- n8n (npm): affected from 2.26.0; fixed in 2.26.2\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-54311/ (Markdown: https://insights.sbomify.com/CVE-2026-54311/index.md)","id":"CVE-2026-54311","markdown":"https://insights.sbomify.com/CVE-2026-54311/index.md","name":"CVE-2026-54311","record":{"aliases":["GHSA-9c38-2mcm-q7f7","MINI-4gmq-mjp3-phq3","ROOT-APP-NPM-CVE-2026-54311"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"n8n workflow automation","requires_auth":"low_privilege","summary":"Authenticated users can pollute the Merge node SQL sandbox to intercept workflow data from other users on multi-user instances.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"n8n","vendor":"n8n"}],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-488","name":"Exposure of Data Element to Wrong Session"}],"description":"n8n is an open source workflow automation platform. Prior to 2.25.7 and 2.26.2, an authenticated user with permission to create or modify workflows could pollute the sandbox used by the Merge node's SQL Query mode. Because the sandbox context was cached and reused across all workflow executions on the instance, prototype mutations introduced by one user's workflow persist into subsequent Merge SQL executions belonging to other users or projects. This allowed a low-privileged attacker to intercept workflow data processed by other users on the same instance. This issue only affects multi-user n8n instances where more than one user has permission to create and execute workflows containing the Merge node in SQL Query mode. This vulnerability is fixed in 2.25.7 and 2.26.2.","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":true,"headline":"n8n: Merge Node SQL Mode Prototype Pollution","id":"CVE-2026-54311","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"n8n:n8n","products":["n8n:n8n"],"type":"other","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"n8n: Microsoft SQL Node Prototype Pollution","id":"CVE-2026-54312"},"packages":[{"ecosystem":"npm","fixed":["2.25.7"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":null,"source":"GHSA-9c38-2mcm-q7f7"},{"ecosystem":"npm","fixed":["2.25.7"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":"pkg:npm/n8n","source":"GHSA-9c38-2mcm-q7f7"},{"ecosystem":"npm","fixed":["2.26.2"],"introduced":["2.26.0"],"last_affected":[],"package":"n8n","purl":null,"source":"GHSA-9c38-2mcm-q7f7"},{"ecosystem":"npm","fixed":["2.26.2"],"introduced":["2.26.0"],"last_affected":[],"package":"n8n","purl":"pkg:npm/n8n","source":"GHSA-9c38-2mcm-q7f7"}],"prev":{"headline":"n8n: SQL Injection in Postgres v1/TimesclaeDB Nodes","id":"CVE-2026-54310"},"products":["n8n"],"published":"2026-06-23","related":[{"cvss_score":10,"headline":"n8n Improper Control of Dynamically-Managed Code Resources","id":"CVE-2025-68613","kev_date_added":"2026-03-11","published":"2025-12-19"},{"cvss_score":10,"headline":"n8n is vulnerable to Remote Code Execution via Arbitrary File Write","id":"CVE-2026-21877","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":10,"headline":"n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling","id":"CVE-2026-21858","kev_date_added":null,"published":"2026-01-07"},{"cvss_score":9.9,"headline":"n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution","id":"CVE-2026-1470","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":9.9,"headline":"n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node","id":"CVE-2025-68668","kev_date_added":null,"published":"2025-12-26"},{"cvss_score":9.5,"headline":"n8n has Unauthenticated Expression Evaluation via Form Node","id":"CVE-2026-27493","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":9.4,"headline":"n8n: HTTP Request Node Pagination Prototype Pollution to RCE","id":"CVE-2026-44789","kev_date_added":null,"published":"2026-06-23"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-06-23","vendors":["n8n-io"]},"summary":"Authenticated users can pollute the Merge node SQL sandbox to intercept workflow data from other users on multi-user instances.","url":"https://insights.sbomify.com/CVE-2026-54311/"}