# CVE-2025-61914: n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox > Attackers with workflow creation permissions can execute arbitrary JavaScript in the n8n editor via stored XSS in the Respond to Webhook node. - **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 26 Dec 2025 - **Updated:** 26 Dec 2025 - **Also known as:** GHSA-58jc-rcg5-95f3 ## What is CVE-2025-61914? 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. ### Official 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2025-61914? 2 open source packages ship an affected version, including n8n. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `n8n` | npm | All versions | 1.114.0 | | `n8n` | npm | All versions | 1.114.0 | Products: N8n N8n. ## How do I fix CVE-2025-61914? Upgrade n8n to 1.114.0 or later. ## Is CVE-2025-61914 being exploited? There is no known exploitation of CVE-2025-61914 in the wild and no public exploit code. ## Other vulnerabilities in N8n N8n - [CVE-2025-68613](https://insights.sbomify.com/CVE-2025-68613/): n8n Improper Control of Dynamically-Managed Code Resources (critical 10.0, exploited in the wild) - [CVE-2026-21877](https://insights.sbomify.com/CVE-2026-21877/): n8n is vulnerable to Remote Code Execution via Arbitrary File Write (critical 10.0) - [CVE-2026-21858](https://insights.sbomify.com/CVE-2026-21858/): n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling (critical 10.0) - [CVE-2026-1470](https://insights.sbomify.com/CVE-2026-1470/): n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution (critical 9.9) - [CVE-2025-68668](https://insights.sbomify.com/CVE-2025-68668/): n8n Vulnerable to Arbitrary Command Execution in Pyodide based Python Code Node (critical 9.9) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-61914 and fix it if it is affected. What 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. Exploitation: There is no known exploitation of CVE-2025-61914 in the wild and no public exploit code. Affected packages and fixed versions: - n8n (npm): affected all versions; fixed in 1.114.0 - n8n (npm): affected all versions; fixed in 1.114.0 Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-61914/ (Markdown: https://insights.sbomify.com/CVE-2025-61914/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61914 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61914 - OSV: https://osv.dev/vulnerability/CVE-2025-61914 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-61914/ Summaries are generated and may contain mistakes; the official description above is the record.