Summary
n8n: Stored DOM XSS via Resource Locator cachedResultUrl
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict workflow creation and editing permissions to fully trusted users only.
- Audit existing workflows for unexpected
cachedResultUrlvalues containing non-HTTP(S) schemes.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Impact
The Resource Locator passes the workflow-persisted cachedResultUrl to window.open() without scheme validation. When a victim opens the crafted workflow and interact with external links, the JavaScript payload runs in the victim's browser.
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.
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 issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Frequently Asked Questions
- What is CVE-2026-65592? CVE-2026-65592 is a high-severity cross-site scripting (XSS) vulnerability in n8n (npm), affecting versions < 1.123.64. It is fixed in 1.123.64, 2.30.1, 2.29.8. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of n8n are affected by CVE-2026-65592? n8n (npm) versions < 1.123.64 is affected.
- Is there a fix for CVE-2026-65592? Yes. CVE-2026-65592 is fixed in 1.123.64, 2.30.1, 2.29.8. Upgrade to this version or later.
- Is CVE-2026-65592 exploitable, and should I be worried? Whether CVE-2026-65592 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-2026-65592 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-2026-65592?
- Upgrade
n8nto 1.123.64 or later - Upgrade
n8nto 2.30.1 or later - Upgrade
n8nto 2.29.8 or later
- Upgrade