Browse / MCP and Tool Server Flaws / CVE-2026-42235
n8n Vulnerable to XSS via MCP OAuth client
- Class
- MCP and Tool Server Flaws (filed by a model that read the advisory)
- Technique
- Cross-site scripting
- Affected
- n8n (npm)
- CVSS
- CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:L
- EPSS
- 0.3% chance of exploitation in 30 days
How it works, in short
An MCP OAuth client name containing script content is rendered unescaped in a notification, running in another user's session when they see it. (Our summary, written by a model. The source text is below.)
Details
Impact
An unauthenticated attacker could register a malicious MCP OAuth client with a crafted client_name. If a victim user authorized the OAuth consent dialog and a second user subsequently revoked that access, a toast notification would render the injected script. Clicking the link would execute arbitrary JavaScript in the victim's authenticated n8n browser session, enabling credential and session token theft, workflow manipulation, or privilege escalation.
Patches
This issue has been fixed in n8n version 2.14.2. Users should upgrade to this version or later to remediate the vulnerability.
Workarounds
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict access to the n8n instance and the MCP OAuth registration endpoint to trusted users only. - Disable MCP server functionality if it is not actively required.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
References
- https://github.com/n8n-io/n8n/security/advisories/GHSA-537j-gqpc-p7fq
- https://nvd.nist.gov/vuln/detail/CVE-2026-42235
- https://github.com/n8n-io/n8n
Source: GitHub Advisory Database, used under CC BY 4.0.