Summary
n8n's Possible Stored XSS in "Respond to Webhook" Node May Execute Outside iframe Sandbox
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.
While session cookies (n8n-auth) are marked HttpOnly and cannot be directly exfiltrated, the vulnerability can facilitate Cross-Site Request Forgery (CSRF)-like actions from within the user’s authenticated session, potentially allowing:
- Unauthorized reading of sensitive workflow data or execution history.
- Unauthorized modification or deletion of workflows.
- Insertion of malicious workflow logic or external data exfiltration steps.
n8n instances that allow untrusted users to create workflows are particularly impacted.
Workarounds
- Restrict workflow creation and modification privileges to trusted users only.
- Avoid using untrusted HTML responses in the “Respond to Webhook” node.
- Use an external reverse proxy or HTML sanitizer to filter responses that include executable scripts.
Impact
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2025-61914 has a CVSS score of 7.3 (High). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.114.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The vulnerability has been patched in v.1.114.0.
Frequently Asked Questions
- What is CVE-2025-61914? CVE-2025-61914 is a high-severity cross-site scripting (XSS) vulnerability in n8n (npm), affecting versions < 1.114.0. It is fixed in 1.114.0. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2025-61914? CVE-2025-61914 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of n8n are affected by CVE-2025-61914? n8n (npm) versions < 1.114.0 is affected.
- Is there a fix for CVE-2025-61914? Yes. CVE-2025-61914 is fixed in 1.114.0. Upgrade to this version or later.
- Is CVE-2025-61914 exploitable, and should I be worried? Whether CVE-2025-61914 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-61914 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-61914? Upgrade
n8nto 1.114.0 or later.