CVE-2026-42235
Unauthenticated OAuth client name injection enables XSS and token theft.
Is CVE-2026-42235 being exploited?
Not confirmed. CVE-2026-42235 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-42235?
CVE-2026-42235 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-42235?
Yes. A fix has been recorded for CVE-2026-42235. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-42235 affect?
CVE-2026-42235 affects n8n. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-42235?
Patch to latest release; review OAuth clients and rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
XSS in consent flow; attacker can steal credentials/tokens, hijack sessions, and may manipulate workflows or escalate privileges.
Patch when possible
- affected< 1.123.32
- affected>= 2.17.0 and < 2.17.4
- affected>= 2.18.0 and < 2.18.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.