Unauthenticated Cross-Project Workflow Execution via Webhook Path-Only Resolution
GHSA-4c7j-qff5-r9cx · published 2026-09-30
- Severity
- Medium
- CVSS score
- 6.3
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.42.1
A dynamic-path webhook URL contains a server-generated identifier that is the only unguessable part of it. Webhook resolution matched on the path alone and ran first, so a request omitting that identifier still resolved to the workflow and executed it. An unauthenticated caller can run a workflow in a project they have no relationship with, under that project's credentials. The same resolver serves the form and MCP routes. Node-level authentication still applies.
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 1.123.83, 2.42.1 and 2.41.4. 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. Enable node-level webhook authentication (Basic, Header, or JWT) on all active Webhook nodes that use dynamic path templates. Deactivate workflows using dynamic-path webhooks until the instance is patched. Apply network-level controls to restrict access to the /webhook/*, /form/*, and /mcp/* routes to trusted sources only. 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.