n8n credential exposure in node execution errors
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.x before 2.43.5, and 2.44.x before 2.44.1 stores credential secrets in execution error data when operations fail in the Git, MongoDB Atlas Vector Store, and Google Cloud Storage nodes. Users who can view a workflow's executions but cannot read the credential can recover Git passwords or tokens, MongoDB database passwords, or Google access tokens from that data.
From the CVE record · VulnCheck
Affected n8n versions can store credential secrets in execution error data when operations fail in the Git, MongoDB Atlas Vector Store, or Google Cloud Storage nodes. Users who can view a workflow’s executions but cannot read its credentials can recover passwords or tokens from that data.
Teams running n8n before 1.123.85, 2.x before 2.43.5, or 2.44.x before 2.44.1 should check their installations.