{"answers":{"affected":"2 open source packages ship an affected version, including n8n. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-61914 in the wild and no public exploit code.","fix":"Upgrade n8n to 1.114.0 or later.","what":"CVE-2025-61914 is a high-severity cross-site scripting vulnerability in N8n N8n, published on 26 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-61914 and fix it if it is affected.\n\nWhat it is: CVE-2025-61914 is a high-severity cross-site scripting vulnerability in N8n N8n, published on 26 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-61914 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- n8n (npm): affected all versions; fixed in 1.114.0\n- n8n (npm): affected all versions; fixed in 1.114.0\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-2025-61914/ (Markdown: https://insights.sbomify.com/CVE-2025-61914/index.md)","id":"CVE-2025-61914","markdown":"https://insights.sbomify.com/CVE-2025-61914/index.md","name":"CVE-2025-61914","record":{"aliases":["GHSA-58jc-rcg5-95f3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"n8n workflow automation","requires_auth":"low_privilege","summary":"Attackers with workflow creation permissions can execute arbitrary JavaScript in the n8n editor via stored XSS in the Respond to Webhook node.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"n8n","vendor":"n8n"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"n8n is an open source workflow automation platform. Prior to version 1.114.0, a stored Cross-Site Scripting (XSS) vulnerability may occur in n8n when using the “Respond to Webhook” node. When this node responds with HTML content containing executable scripts, the payload may execute directly in the top-level window, rather than within the expected sandbox introduced in version 1.103.0. This behavior can enable a malicious actor with workflow creation permissions to execute arbitrary JavaScript in the context of the n8n editor interface. This issue has been patched in version 1.114.0. Workarounds for this issue involve restricting workflow creation and modification privileges to trusted users only, avoiding use of untrusted HTML responses in the “Respond to Webhook” node, and using an external reverse proxy or HTML sanitizer to filter responses that include executable scripts.","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's Possible Stored XSS in \"Respond to Webhook\" Node May Execute Outside iframe Sandbox","id":"CVE-2025-61914","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"n8n:n8n","products":["n8n:n8n"],"type":"xss","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"OpenPrinting CUPS vulnerable to stack based out-of-bound write","id":"CVE-2025-61915"},"packages":[{"ecosystem":"npm","fixed":["1.114.0"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":null,"source":"GHSA-58jc-rcg5-95f3"},{"ecosystem":"npm","fixed":["1.114.0"],"introduced":["0"],"last_affected":[],"package":"n8n","purl":"pkg:npm/n8n","source":"GHSA-58jc-rcg5-95f3"}],"prev":{"headline":"Flowise is vulnerable to arbitrary file read, arbitrary file write","id":"CVE-2025-61913"},"products":["n8n"],"published":"2025-12-26","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":"total"},"state":"PUBLISHED","updated":"2025-12-26","vendors":["n8n-io"]},"summary":"Attackers with workflow creation permissions can execute arbitrary JavaScript in the n8n editor via stored XSS in the Respond to Webhook node.","url":"https://insights.sbomify.com/CVE-2025-61914/"}