N8N · GHSA-jmcg-c7p5-q69g · Package
FIX → >= 1.123.89 +3
When the n8n NocoDB node downloads attachments, it fetches the URL stored in the record without checking it against the NocoDB host, so the NocoDB API token is sent to whatever host the URL names. Anyone who can edit an attachment cell in a NocoDB base can make the token go to a host they control when the workflow runs.
first public Oct 28, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run n8n with the NocoDB node and "Download Attachments" enabled are exposed, and the risk grows with the number of people who can edit NocoDB attachment cells. Instances without the NocoDB node, or with attachment download turned off, are not affected by this flaw. The advisory's workarounds are to disable that option, limit editor access, rotate tokens, and set N8N_SSRF_PROTECTION_ENABLED=true, but it says these are short-term only.
Not affected if attachments-download-disabled, fixed-version, no-nocodb-node
Who cares n8n, nocodb, self-hosted, workflow-automation
n8n --version and compare it with the fixed versions below.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.
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 upgrading is not immediately possible, administrators should consider the following temporary mitigations:
N8N_SSRF_PROTECTION_ENABLED=true.These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to >= 1.123.89 +3
1.123.89 on the 1.x line2.45.5 on the 2.45 line2.46.1 on the 2.46 line3.0.1 on the 3.x line