Skip to main content
VulnerabilityPublished

CVE-2026-42230: n8n · Open Redirect

Affects n8nSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.1 Medium · fixed in 2.18.1 : update n8n when convenient.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% 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:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
n8n-ion8nAffected
  • >=2.18.0 <2.18.1
Fixed in
  • 2.18.1
n8n-ion8nAffected
  • >=2.17.0 <2.17.4
Fixed in
  • 2.17.4
n8n-ion8nAffected
  • <1.123.32
Fixed in
  • 1.123.32
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threatsAffected
  • <1.123.32
Fixed in
  • 1.123.32

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 in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to these or later versions to remediate the vulnerability. No vendor advisory content contradicts this; therefore, upgrading is the recommended mitigation.

Description

n8n is an open source workflow automation platform. Prior to versions 1.123.32, 2.17.4, and 2.18.1, the /mcp-oauth/register endpoint accepted OAuth client registrations without authentication, allowing arbitrary redirect_uri values to be registered. When a user denies the MCP OAuth consent dialog, the handleDeny handler redirects the user to the registered redirect_uri without validation, enabling an open redirect to an attacker-controlled URL. An attacker can craft a phishing link and send it to a victim; if the victim clicks "Deny" on the consent page, they are silently redirected to an external site. This issue has been patched in versions 1.123.32, 2.17.4, and 2.18.1.

References

Community reviews

Loading reviews…