{"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-86078 in the wild and no public exploit code.","fix":"Upgrade n8n to a fixed version for your release line: 2.37.7 or 2.38.2.","what":"CVE-2026-86078 is a medium-severity vulnerability in N8n N8n, published on 8 Sep 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-86078 and fix it if it is affected.\n\nWhat it is: CVE-2026-86078 is a medium-severity vulnerability in N8n N8n, published on 8 Sep 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-86078 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- n8n (npm): affected all versions; fixed in 2.37.7\n- n8n (npm): affected all versions; fixed in 2.37.7\n- n8n (npm): affected from 2.38.0; fixed in 2.38.2\n- n8n (npm): affected from 2.38.0; fixed in 2.38.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-86078/ (Markdown: https://insights.sbomify.com/CVE-2026-86078/index.md)","id":"CVE-2026-86078","markdown":"https://insights.sbomify.com/CVE-2026-86078/index.md","name":"CVE-2026-86078","record":{"aliases":["GHSA-679f-58pq-4v2c","MINI-2xqh-6wch-52vm"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"n8n workflow automation","requires_auth":"low_privilege","summary":"Attackers can cause denial of service in n8n by submitting workflows with malicious keys that pollute the prototype, requiring an upgrade to fix.","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:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"n8n is an open source workflow automation platform. Prior to 2.37.7 and 2.38.2, the Instance AI workflow summary used node names and connection keys from stored workflows as ordinary object keys. A workflow submitted through the REST API could contain __proto__ or constructor, causing nested writes to reach Object.prototype in the main n8n process and disrupt later requests. The affected function is summarizeWorkflowStructure in packages/@n8n/instance-ai/src/tools/workflows/summarize-workflow.ts. This issue is fixed in versions 2.37.7 and 2.38.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: Prototype Pollution via Workflow Structure Summary Can Lead to Denial of Service","id":"CVE-2026-86078","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"n8n:n8n","products":["n8n:n8n"],"type":"other","year":"2026"},"n_packages":4,"n_references":3,"next":{"headline":"n8n: Path Injection in Elasticsearch and ElasticSecurity Nodes via Unencoded Identifiers","id":"CVE-2026-86079"},"packages":[{"ecosystem":"npm","fixed":["2.37.7"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":null,"source":"GHSA-679f-58pq-4v2c"},{"ecosystem":"npm","fixed":["2.37.7"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":"pkg:npm/n8n","source":"GHSA-679f-58pq-4v2c"},{"ecosystem":"npm","fixed":["2.38.2"],"introduced":["2.38.0"],"last_affected":[],"package":"n8n","purl":null,"source":"GHSA-679f-58pq-4v2c"},{"ecosystem":"npm","fixed":["2.38.2"],"introduced":["2.38.0"],"last_affected":[],"package":"n8n","purl":"pkg:npm/n8n","source":"GHSA-679f-58pq-4v2c"}],"prev":{"headline":"n8n: Anonymous Approval-Gate Bypass via Reused resumeToken over the Chat WebSocket","id":"CVE-2026-86077"},"products":["n8n"],"published":"2026-09-08","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-09-09","vendors":["n8n-io"]},"summary":"Attackers can cause denial of service in n8n by submitting workflows with malicious keys that pollute the prototype, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2026-86078/"}