UTC
Medium

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
What it is

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.

What to do

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 you cannot upgrade yet

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.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.961.123.96
n8nnpm< 2.47.62.47.6
n8nnpm< 2.48.32.48.3
n8nnpm< 3.2.23.2.2

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].