Description
n8n versions before 1.123.64 fail to properly mask custom HTTP header credentials in LLM sub-node execution data, writing plaintext API keys and secrets to workflow execution records. Authenticated users with access to execution data can read exposed header values and credentials that persist in the database and can be exported.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| n8n-io | n8n | < 1.123.64, 2.30.0 – < 2.30.1, 2.0.0-rc.0 – < 2.29.8 | 1.123.64 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| npm | n8n | < 1.123.64 | 1.123.64 | GHSA-89gh-3pgc-v5h2 |
| npm | n8n | >= 2.30.0, < 2.30.1 | 2.30.1 | GHSA-89gh-3pgc-v5h2 |
| npm | n8n | >= 2.0.0-rc.0, < 2.29.8 | 2.29.8 | GHSA-89gh-3pgc-v5h2 |
References
- GitHub Security Advisory (GHSA-89gh-3pgc-v5h2) vendor-advisory
- VulnCheck Advisory: n8n before 1.123.64 Credential Exposure via LLM Node Execution Data third-party-advisory