UTC
Medium

NocoDB Node Sends Its API Token to Attacker-Chosen Hosts When Downloading Attachments

GHSA-jmcg-c7p5-q69g · published 2026-10-28

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

When the NocoDB node reads rows with "Download Attachments" enabled, it takes the attachment URL directly from the record content and fetches it using the configured NocoDB credential. The target host is never compared against the credential's own host, so any party who can write to an attachment cell in a NocoDB base can cause the credential's API token to be sent to a host of their choosing when the workflow next executes.

What to do

Upgrade n8n to 3.0.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.89, 2.45.5, 2.46.1 and 3.0.1. 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. Disable the "Download Attachments" option on all active NocoDB nodes until the instance is patched. Audit NocoDB base memberships and remove editor access from any users who are not fully trusted. Rotate any NocoDB API tokens used by affected workflows and audit recent execution logs for unexpected outbound requests. Enable SSRF protection by setting N8N_SSRF_PROTECTION_ENABLED=true. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 1.123.891.123.89
n8nnpm< 2.45.52.45.5
n8nnpm< 2.46.12.46.1
n8nnpm< 3.0.13.0.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].