n8n before 1.123.69 Credential Leak via GraphQL Node Error
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 versions before 1.123.69, 2.33.4, and 2.34.1 contain an information disclosure vulnerability in the GraphQL node. When a GraphQL request fails at the connection level, the node re-throws the underlying HTTP client error unchanged instead of wrapping it in n8n's standard error type. That error contains the live request's headers, including a decrypted credential secret, which the execution engine persists verbatim. Any authenticated user able to read the resulting execution can retrieve the decrypted credential secret from the stored run data.
From the CVE record · VulnCheck
In n8n versions before 1.123.69, 2.33.4, and 2.34.1, a connection-level GraphQL request failure can cause the node to store an error containing a decrypted credential secret in execution data. An authenticated user who can read that execution can retrieve the secret; no additional user interaction is described.
Teams running n8n versions before 1.123.69, 2.33.4, or 2.34.1 should check their deployments.