CVE-2025-52478

Workarounds

Apart from updating to the fixed version, n8n instance administrators can:

• Configure a reverse proxy to serve webhook requests from a different domain [docs].
• Disable or restrict use of the Form Trigger node, particularly the HTML element type.
• Use a Content Security Policy (CSP) to block execution of inline scripts and disallow use of srcdoc.

References

• OWASP XSS Prevention Cheat Sheet
• MDN: iframe srcdoc attribute
• HTML: onerror attribute

A stored Cross-Site Scripting (XSS) vulnerability was identified in n8n, specifically in the Form Trigger node's HTML form element. An authenticated attacker can inject malicious HTML via an <iframe> with a srcdoc payload that includes arbitrary JavaScript execution. The attacker can also inject malicious Javascript by using <video> coupled <source> using an onerror event.

While using iframe or a combination of video and source tag, this vulnerability allows for Account Takeover (ATO) by exfiltrating n8n-browserId and session cookies from authenticated users who visit a maliciously crafted form. Using these tokens and cookies, an attacker can impersonate the victim and change account details such as email addresses, enabling full control over the account, especially if 2FA is not enabled.

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-52478 has a CVSS score of 8.7 (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.98.2); upgrading removes the vulnerable code path.

Kodem intelligence

The issue was addressed in PR #16329. Users should upgrade to version >=1.98.2.

1. What is CVE-2025-52478? CVE-2025-52478 is a high-severity cross-site scripting (XSS) vulnerability in n8n (npm), affecting versions >= 1.77.0, < 1.98.2. It is fixed in 1.98.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2025-52478? CVE-2025-52478 has a CVSS score of 8.7 (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.
3. Which versions of n8n are affected by CVE-2025-52478? n8n (npm) versions >= 1.77.0, < 1.98.2 is affected.
4. Is there a fix for CVE-2025-52478? Yes. CVE-2025-52478 is fixed in 1.98.2. Upgrade to this version or later.
5. Is CVE-2025-52478 exploitable, and should I be worried? Whether CVE-2025-52478 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
6. What actually determines whether CVE-2025-52478 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.
7. How do I fix CVE-2025-52478? Upgrade n8n to 1.98.2 or later.