Skip to content
Blog

n8n Cross-Site Scripting Vulnerability (CVE-2026-42235) — High Severity

N8N-Banner-ucartz
In this article
  1. CVE Details
  2. Affected Products
  3. Current Status
  4. Severity Level
  5. Possible Solutions
  6. References

n8n is a powerful open-source platform designed to automate workflows and connect various applications without needing extensive coding. It’s a favorite among developers and IT professionals for streamlining tasks and boosting efficiency. However, a recently discovered vulnerability, tracked as CVE-2026-42235, highlighted a significant security risk within its system. This flaw, a type of Cross-Site Scripting (XSS), could allow attackers to execute malicious code within a user’s browser, potentially leading to unauthorized actions and data theft.

CVE Details

This vulnerability, identified as CVE-2026-42235, affects the n8n platform. It was publicly disclosed on May 4, 2026, and involves a reflected Cross-Site Scripting (XSS) flaw in how n8n handles MCP OAuth client registration. The issue is considered “Analyzed,” meaning its details have been thoroughly investigated and confirmed.

Affected Products

The vulnerability impacts n8n versions prior to 1.123.32, 2.17.4, and 2.18.1. Specifically, any n8n installation running an older version than these patched releases is susceptible. Users of the n8n Enterprise edition, including version 2.18.0, are particularly advised to check their versions.

Current Status

The vulnerability’s status is “Analyzed.” This indicates that the n8n development team and security researchers have thoroughly examined the issue, understood its root cause, and confirmed its impact. Importantly, patches have been released, providing a clear pathway for users to secure their installations.

Severity Level

CVE-2026-42235 has been assigned a High severity rating with a CVSS score of 8.8. While not the absolute highest, a high severity indicates a serious risk that requires prompt attention. Exploiting this XSS flaw could allow an unauthenticated attacker to steal user credentials or session tokens, manipulate existing workflows, or escalate their privileges within an authenticated n8n browser session.

Possible Solutions

The best and most recommended solution is to upgrade your n8n instance to a patched version immediately. The issue has been fixed in:

  • n8n version 1.123.32 or later
  • n8n version 2.17.4 or later
  • n8n version 2.18.1 or later

For those who cannot upgrade immediately, temporary mitigation steps can be considered:

  • Restrict access to your n8n instance and its MCP OAuth registration endpoint to only trusted users.
  • If not actively in use, consider disabling the MCP server functionality.

Please note that these workarounds do not fully eliminate the risk and should only serve as short-term measures until a full upgrade can be performed. Always follow n8n’s official upgrade procedures to ensure a smooth and secure transition.

References

https://github.com/n8n-io/n8n/security/advisories/GHSA-537j-gqpc-p7fq

Share
Alex Joseph

Alex Joseph

Alex Joseph is a Senior Support Staff professional with deep experience in server management, web hosting technologies, and cybersecurity operations. He works daily with Linux servers, cloud platforms, performance tuning, and security hardening, giving him strong real-world technical knowledge. Along with his support role, he write about security best practices, hosting infrastructure, and software management.

Related updates

Start Building Today

Ready to Get Started?

VPS, dedicated servers, streaming and managed hosting with 24/7 support from the Ucartz team.