n8n credential exposure via external sub-workflow sources
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 before 1.123.85, 2.43.5, and 2.44.1 contains a credential guard bypass vulnerability that allows editors of shared workflows to use restricted credentials by loading sub-workflows from URLs or local files. Attackers can configure the Execute Sub-workflow node with source url or localFile to serve content that resolves project credentials and returns their decrypted values.
From the CVE record · VulnCheck
n8n has a credential guard bypass in the Execute Sub-workflow node. An attacker with editor access to a shared workflow can load a sub-workflow from a URL or local file to use restricted project credentials and obtain their decrypted values. No additional user interaction is described.
Teams running n8n versions before the applicable fixed releases 1.123.85, 2.43.5, or 2.44.1 should check their deployments.