Integration Nodes Send Authenticated Requests to Unintended API Endpoints
GHSA-c772-hjfp-gfc2 · published 2026-11-13
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 3.2.2
Multiple n8n nodes built the URL path of their API requests from node parameters such as record, table or resource IDs. These values were not encoded, so a value containing relative path segments could change which endpoint of the same service the request reached. Where a workflow passed untrusted input, such as a webhook body, into one of these parameters, a caller could make the node read, modify or delete resources outside the workflow's intended scope, with the privileges of the node's stored credential.
Upgrade n8n to 3.2.2 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.96, 2.47.6, 2.48.3 and 3.2.2. 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. Audit active workflows and ensure that node parameters holding record, table or resource IDs do not incorporate untrusted external data via expressions. Apply network-level controls to restrict access to webhook endpoints that feed into these workflows. Limit the permissions of the credentials used by affected workflows to the resources those workflows need. Deactivate affected workflows until the instance is patched. 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.