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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/n8n-io/n8n/security/advisories/GHSA-89gh-3pgc-v5h2 Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.1 · n8nNVD modified 2026-10-24 17:10
Affected (CPE criteria) 4
cpe:2.3:a:n8n:n8n:*:*:*:*:community:node.js:*:*cpe:2.3:a:n8n:n8n:*:*:*:*:enterprise:node.js:*:*cpe:2.3:a:n8n:n8n:2.30.0:*:*:*:community:node.js:*:*cpe:2.3:a:n8n:n8n:2.30.0:*:*:*:enterprise:node.js:*:*
References 2
- https://github.com/n8n-io/n8n/security/advisories/GHSA-89gh-3pgc-v5h2 Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/n8n-before-credential-exposure-via-llm-node-execution-data Third Party Advisory