CVE-2026-42235: n8n: XSS via MCP OAuth client

Published Apr 29, 2026
·
Updated

Impact An unauthenticated attacker could register a malicious MCP OAuth client with a crafted clientname. 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.

Other sources

n8n is an open source workflow automation platform. Prior to versions 1.123.32, 2.17.4, and 2.18.1, an unauthenticated attacker could register a malicious MCP OAuth client with a crafted clientname. 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. This issue has been patched in versions 1.123.32, 2.17.4, and 2.18.1.

MITRE

Affected Software

6 affected componentsFixes available
npm/n8n>=2.17.0<2.17.4
2.17.4
npm/n8n>=2.18.0<2.18.1
2.18.1
npm/n8n<1.123.32
1.123.32
n8n N8n Node.js<1.123.32
n8n N8n Node.js>=2.17.0<2.17.4
n8n N8n Node.js=2.18.0

Event History

Apr 29, 2026
Advisory Published
via GitHub·09:23 PM
Data Sourced
via GitHub·09:23 PM
DescriptionSeverityWeaknessAffected Software
May 4, 2026
CVE Published
via MITRE·06:38 PM
Data Sourced
via MITRE·06:38 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-42235?

The severity of CVE-2026-42235 is considered medium due to the potential for cross-site scripting (XSS) attacks.

2

How do I fix CVE-2026-42235?

To fix CVE-2026-42235, upgrade to n8n versions 2.17.4, 2.18.1, or 1.123.32 or later.

3

What kind of attacks does CVE-2026-42235 facilitate?

CVE-2026-42235 facilitates cross-site scripting (XSS) attacks through unauthorized OAuth client registration.

4

Who is affected by CVE-2026-42235?

Users of n8n versions between 2.17.0 and 2.17.4, 2.18.0 and 2.18.1, and versions prior to 1.123.32 are affected by CVE-2026-42235.

5

Can CVE-2026-42235 be exploited without authentication?

Yes, CVE-2026-42235 can be exploited by unauthenticated attackers, increasing the risk of user exposure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203