Quick Base Node Allows Filter Injection Through the Where Parameter
GHSA-65mv-v8rp-54wc · published 2026-10-14
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 2.44.1
The Quick Base node sends the Where filter to the Quick Base API as raw query text. Where a workflow builds this filter from untrusted input, such as webhook data, an external caller can change the filter logic: a Get Many returns every record in the table and a Delete removes every record, with the privileges of the workflow's credential. Use the new Where Parameters option for dynamic values; a Where filter built with an expression stays unsafe.
Upgrade n8n to 2.44.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.85, 2.44.1, and 2.43.5. 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 that use the Quick Base node and ensure the Where parameter does not incorporate untrusted external data via expressions. Apply network-level controls to restrict access to webhook endpoints that feed into Quick Base record:delete or record:getAll operations. Disable the Quick Base node by adding n8n-nodes-base.quickBase to the NODES_EXCLUDE environment variable if it is not required. If the node is used as an agent tool, review and restrict which agents have access to it. …
- 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.