# CVE-2026-42230: n8n Open Redirect — Fixed in 1.123.32

📦 npm

Not in CISA KEV

# CVE-2026-42230 — n8n

CVE-2026-42230 is a Open Redirect vulnerability in n8n. A fix is available for n8n — see the affected versions and patch details below.

n8n: Open Redirect in MCP OAuth Consent Flow

Also known as[GHSA-f6x8-65q6-j9m9](/vulnerability/GHSA-f6x8-65q6-j9m9)

Published

May 4, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-42230.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

0.00%0.27%0.53%0.80%0.1%0.2%Jun 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## Real-World Exposure

3 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

36other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`n8n`npm

152Kdownloads / week

## Description

### Impact

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.

### Patches

The issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

### Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

-   Restrict network access to the n8n instance to prevent untrusted users from reaching the MCP OAuth endpoints.
-   Limit access to the n8n instance to fully trusted users only.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

## Affected Packages

3 total 3 fixed

Ecosystem

Package

Vulnerable range

Fix

📦npm

`n8n` 

all versions

1.123.32`npm install n8n@1.123.32`

📦npm

`n8n` 

≥ 2.18.0&&< 2.18.1

2.18.1`npm install n8n@2.18.1`

📦npm

`n8n` 

≥ 2.0.0&&< 2.17.4

2.17.4`npm install n8n@2.17.4`

## Affected Products

1 product · 3 configurations

Application

`n8n`n8n

≥ 2.17.0 && < 2.17.4

1 version

2.18.0

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update n8n to 1.123.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-42230 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
    

## Frequently Asked Questions

\## Impact 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. ## Patches The issue has been fixed in n8n versions 1.123.32, 2.17.4,

O3 Security · Impact-Aware SCA

### Is CVE-2026-42230 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)