n8n before 1.123.73 Credential Exposure via Error Logging
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.73, 2.35.4, and 2.36.2 contains a credential exposure vulnerability in the Strapi, SeaTable, and Mailcheck nodes. These nodes send their decrypted credentials to the authentication endpoint via the raw legacy HTTP helper outside any error handling, causing the plaintext secret to be persisted in execution error data. Any authenticated user can read the plaintext secret from their own execution through the REST API, bypassing the blank-value redaction enforced by the credentials API.
From the CVE record · VulnCheck
Affected n8n versions can persist decrypted credentials in execution error data when the Strapi, SeaTable, or Mailcheck nodes send them to an authentication endpoint. An authenticated user can read plaintext secrets from their own execution through the REST API, bypassing credentials API redaction.
Teams running n8n versions before 1.123.73, 2.35.4, or 2.36.2 should check their deployments.