UTC
Medium

Unescaped Parameter Interpolation into Third-Party Query Languages Enables Filter Bypass and Bulk Data Disclosure

GHSA-5pg9-2vqx-r6jm · published 2026-09-16

Severity
Medium
CVSS score
6.9
Chance of exploitation (EPSS)
No CVE
Fixed in
2.40.1
What it is

The SendGrid, Freshservice, and ServiceNow nodes constructed third-party query or filter strings by directly interpolating bindable node parameters into DSL literals without neutralising the delimiter. When such a parameter is bound to untrusted external input an attacker can break out of the intended literal and widen a single-record lookup into a match-all or filter-bypass query against the upstream service. This can expose data beyond the intended record within the upstream tenant's scope, including contact lists, ticket and asset records, and directory entries. Exploitation requires the workflow to be configured to bind the vulnerable node parameter to untrusted external input.

What to do

Upgrade n8n to 2.40.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.40.1 and 2.39.6. 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 workflows that use the SendGrid, Freshservice, or ServiceNow nodes and ensure that filter or query parameters are not bound directly to untrusted external input such as webhook or HTTP request fields. Deactivate webhook-triggered workflows that pass external input into the affected nodes 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< 2.39.62.39.6
n8nnpm< 2.40.12.40.1

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].