n8n before 1.123.69 Allowed-Domains Bypass via GraphQL Node
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.69, 2.x before 2.33.4, and 2.x before 2.34.1 contain an allowed-domains bypass in the GraphQL node. When the node's Authentication parameter is set to expression mode, every authentication-gated credential selector is treated as active; if two credentials of different types are attached, the node enforces the allowed-domains policy of only the first credential while still attaching material from both. An authenticated user with workflow-authoring rights can thereby send a domain-restricted credential to an attacker-controlled endpoint, exfiltrating it with the leaked credential's permissions.
From the CVE record · VulnCheck
The GraphQL node can bypass credential allowed-domains restrictions when its Authentication parameter is set to expression mode and two credentials of different types are attached. An authenticated user with workflow-authoring rights can send a restricted credential to an attacker-controlled endpoint.
Teams running n8n before 1.123.69, 2.x before 2.33.4, or 2.x before 2.34.1 should check their installations.