n8n API token exposure in NocoDB attachment downloads
n8n-io n8n
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n-io n8n
| Product | Affected | Fixed in |
|---|---|---|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
| n8n-io n8n |
|
|
n8n before 1.123.89 contains a credential leakage vulnerability in the NocoDB node that sends the configured NocoDB API token to attacker-chosen hosts when downloading attachments. Attackers with write access to a NocoDB attachment cell can insert a URL to their host, capturing the API token when the workflow executes with Download Attachments enabled.
From the CVE record · VulnCheck
n8n before 1.123.89 can leak the configured NocoDB API token when its NocoDB node downloads attachments. An attacker with write access to a NocoDB attachment cell can place a URL pointing to their host and capture the token when the workflow executes with Download Attachments enabled.
Engineers running n8n before 1.123.89 who use the NocoDB node should check their workflows.