CVE-2026-42235: n8n · Improper Neutralization of Alternate XSS Syntax
Affects n8nSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 2.18.1 : patch n8n soon.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.18.1, 2.17.4, 1.123.32
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:H/SI:H/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 4 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Upgrade n8n to 2.18.1, 2.17.4 or 1.123.32; n8n-io/n8n to 1.123.32.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
| n8n-ion8n | Affected
| Fixed in
|
GitHubn8n-io/n8npkg:github/n8n-io/n8nOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available and has been released in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to these or later versions to remediate this vulnerability. No additional vendor advisory content is provided, so patching is the primary recommended mitigation.
Description
CVE-2026-42235 is a high-severity vulnerability in the n8n workflow automation platform affecting versions prior to 1.123.32, 2.17.4, and 2.18.1. It allows an unauthenticated attacker to register a malicious OAuth client with a crafted client_name that leads to improper neutralization of alternate XSS syntax. When a victim user authorizes the OAuth consent and another user revokes access, a toast notification renders injected script, enabling execution of arbitrary JavaScript in the victim's authenticated session. This can result in credential and session token theft, workflow manipulation, or privilege escalation.