Shared Prototype Mutation Through the MCP Workflow-Validation Interpreter Allows Owner Account Takeover
GHSA-5jr4-xmvf-frmj · published 2026-09-30
- Severity
- High
- CVSS score
- 7.7
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.42.1
The MCP workflow-validation tool evaluates caller-supplied code in the main process through an interpreter that reads inherited properties and allows assignment onto shared prototypes. A member holding only a read grant can replace a built-in method with one that returns a truthy value, which makes a server-side permission check accept a scope they do not hold. The reporter drove this to a full takeover of the instance owner's account. Accounts protected by MFA are not affected.
Upgrade n8n to 2.42.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 2.41.4 and 2.42.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: Disable the instance-level MCP server if it is not required. Restrict n8n instance access to fully trusted users only. Enable MFA on all owner and admin accounts to prevent password-reset links from being usable even if obtained. Audit and revoke workflow:read MCP OAuth grants from any users who do not require them. 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.