Open Redirect via MCP OAuth Dynamic Client Registration
GHSA-rc3w-8jc8-7x3w · published 2026-10-28
- Severity
- Medium
- CVSS score
- 5.1
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 3.0.1
The MCP OAuth registration and authorization endpoints are enabled by default and require no authentication. Any caller could register an OAuth client with an arbitrary redirect_uri, and a crafted authorization URL then redirected the visitor to that URI before the instance's checks ran, turning the n8n instance into an open redirector. No tokens or session data were included in the redirect. A victim had to open the crafted URL.
Upgrade n8n to 3.0.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The issue has been fixed in n8n versions 1.123.89, 2.45.5, 2.46.1 and 3.0.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict n8n instance access to fully trusted users only. Apply network-level controls or a reverse-proxy rule to block unauthenticated access to the /mcp-oauth/register and /mcp-oauth/authorize endpoints. Educate users not to follow unsolicited links pointing to your n8n instance's OAuth endpoints. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (published by n8n). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.