INCIDENT MAP

Browse / MCP and Tool Server Flaws / CVE-2026-42230

n8n has Open Redirect in MCP OAuth Consent Flow

CVE-2026-42230 ยท 2026-04-29 moderate

Class
MCP and Tool Server Flaws (filed by a model that read the advisory)
Technique
Other weaknesses
Affected
n8n (npm)
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

Unauthenticated OAuth client registration lets an attacker set an arbitrary redirect URI, which the consent deny handler follows without validation. (Our summary, written by a model. The source text is below.)

Details

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.

References

Source: GitHub Advisory Database, used under CC BY 4.0.