N8n: Duplicate Advisory: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data
n8n versions before 1.123.64 do not properly mask custom HTTP header credentials in LLM sub-node execution data. This results in plaintext API keys and secrets being written to workflow execution records. Authenticated users with access to these execution records can read and export these exposed credentials, which persist in the database. This vulnerability is categorized under CWE-532 (Exposure of Sensitive Information). The advisory is a duplicate and has been withdrawn in favor of GHSA-89gh-3pgc-v5h2.
AI Analysis
Technical Summary
The vulnerability in n8n prior to version 1.123.64 involves failure to mask sensitive custom HTTP header credentials within LLM sub-node execution data. Consequently, API keys and secrets are stored in plaintext in workflow execution records. Authenticated users with permission to view execution data can access these credentials, which remain stored in the database and can be exported. This exposure of sensitive information could lead to unauthorized use of API keys and secrets if an attacker gains access to execution data. The advisory has been withdrawn as a duplicate of GHSA-89gh-3pgc-v5h2.
Potential Impact
Sensitive API keys and secrets in custom HTTP headers are exposed in plaintext within workflow execution records. This exposure allows any authenticated user with access to execution data to read and export these credentials, increasing the risk of credential compromise and unauthorized access to associated services. The credentials persist in the database, extending the window of exposure until remediated.
Mitigation Recommendations
A fix is available in n8n version 1.123.64 and later, which properly masks custom HTTP header credentials in execution data. Users should upgrade to version 1.123.64 or newer to remediate this vulnerability. Since this advisory is a duplicate and withdrawn, refer to the original advisory GHSA-89gh-3pgc-v5h2 for detailed remediation instructions.
N8n: Duplicate Advisory: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data
Description
n8n versions before 1.123.64 do not properly mask custom HTTP header credentials in LLM sub-node execution data. This results in plaintext API keys and secrets being written to workflow execution records. Authenticated users with access to these execution records can read and export these exposed credentials, which persist in the database. This vulnerability is categorized under CWE-532 (Exposure of Sensitive Information). The advisory is a duplicate and has been withdrawn in favor of GHSA-89gh-3pgc-v5h2.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in n8n prior to version 1.123.64 involves failure to mask sensitive custom HTTP header credentials within LLM sub-node execution data. Consequently, API keys and secrets are stored in plaintext in workflow execution records. Authenticated users with permission to view execution data can access these credentials, which remain stored in the database and can be exported. This exposure of sensitive information could lead to unauthorized use of API keys and secrets if an attacker gains access to execution data. The advisory has been withdrawn as a duplicate of GHSA-89gh-3pgc-v5h2.
Potential Impact
Sensitive API keys and secrets in custom HTTP headers are exposed in plaintext within workflow execution records. This exposure allows any authenticated user with access to execution data to read and export these credentials, increasing the risk of credential compromise and unauthorized access to associated services. The credentials persist in the database, extending the window of exposure until remediated.
Mitigation Recommendations
A fix is available in n8n version 1.123.64 and later, which properly masks custom HTTP header credentials in execution data. Users should upgrade to version 1.123.64 or newer to remediate this vulnerability. Since this advisory is a duplicate and withdrawn, refer to the original advisory GHSA-89gh-3pgc-v5h2 for detailed remediation instructions.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fmvg-vhqq-r2mj
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a616bd09c2644c7f80dbef9
Added to database: 07/23/2026, 01:18:08 UTC
Last enriched: 07/23/2026, 01:23:14 UTC
Last updated: 09/04/2026, 05:54:33 UTC
Views: 81
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.