The workflow automation platform n8n has addressed a security flaw that could allow attackers to redirect users to malicious websites. This vulnerability, identified as CVE-2026-42230, falls under the category of an “Open Redirect” and primarily poses a risk through phishing attacks.
This issue stems from an unauthenticated endpoint within n8n that improperly handled OAuth client registrations. Attackers could register arbitrary redirect URLs without needing any authentication. If a user then interacted with a crafted phishing link and chose to “Deny” the MCP OAuth consent dialog, they would be silently sent to an attacker’s chosen external site instead of a legitimate one. This makes it easier for bad actors to trick users into visiting harmful pages, potentially leading to further compromise.
CVE Details
- Product: n8n (open-source workflow automation platform)
- CVE ID: CVE-2026-42230
- Published Date: May 4, 2026
- Last Modified: November 11, 2026
- Severity: Medium
- Status: Analyzed
Affected Products
This vulnerability impacts versions of n8n prior to the following:
- n8n versions before 1.123.32
- n8n versions before 2.17.4
- n8n versions before 2.18.1
Users running any n8n instance older than these specific versions are at risk.
Current Status
The vulnerability has been thoroughly analyzed, and the developers at n8n have released updates to address the issue. Patches are available, and users are strongly encouraged to update their installations.
Severity Level
Rated as Medium with a CVSS score of 6.1, this vulnerability has the potential for significant user impact, particularly through targeted phishing campaigns. While it doesn’t directly allow an attacker to take over the n8n system, it creates a deceptive pathway that can be exploited to lead users to other malicious sites. This could compromise user credentials or expose them to other cyber threats.
Possible Solutions
The most effective way to protect your n8n instance and its users from this open redirect vulnerability is to apply the available patches.
- Upgrade Immediately: It is crucial to upgrade your n8n installation to version 1.123.32, 2.17.4, 2.18.1, or any later version. These updates contain the necessary fixes to prevent unauthenticated redirect URI registrations.
- Temporary Mitigations (if immediate upgrade is not possible):
- Restrict Network Access: Limit network access to your n8n instance, particularly blocking untrusted users from reaching the
/mcp-oauth/registerendpoint and other MCP OAuth related services. - Limit User Access: Ensure that only fully trusted users have access to your n8n instance.
Please note that these workarounds do not completely eliminate the risk and should only be considered short-term measures until a full upgrade can be performed.
- Restrict Network Access: Limit network access to your n8n instance, particularly blocking untrusted users from reaching the
Staying updated with the latest security patches is always the best defense against known vulnerabilities. (Consider linking to internal articles on “Understanding Phishing Attacks” or “Best Practices for Web Application Security”.)
References
https://github.com/n8n-io/n8n/security/advisories/GHSA-f6x8-65q6-j9m9