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

Impact

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.

Patches

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.

Workarounds

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.