CVE-2026-65589: n8n before 1.123.64 Credential Exposure via LLM Node Execution Data
Impact Custom HTTP headers configured in credentials for certain LLM sub-nodes (including OpenAI, Anthropic, and Lemonade) are masked in the n8n UI but are written in plaintext into execution data during workflow runs. Any authenticated user with access to the execution data for an affected workflow can read the header names and values, which typically contain API keys or other secrets.
Because execution data can be persisted to the database and exported, leaked values may remain accessible beyond the lifetime of a single execution.
This issue only affects instances where workflows use LLM sub-nodes with custom headers defined in their credentials.
Patches The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Users should upgrade to one of these versions or later to remediate the vulnerability.
Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Restrict access to execution data to fully trusted users only. - Avoid configuring custom headers in LLM node credentials; use alternative authentication mechanisms where possible. - Rotate any API keys or secrets that may have been stored as custom header values in affected credentials.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Other sources
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.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.29.8 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.30.1 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 1.123.64 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.64 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.29.8 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.30.1 - Configuration
In affected LLM sub-node credentials, avoid configuring custom HTTP headers and instead use alternative authentication mechanisms where possible, since custom headers are written in plaintext to execution data.
n8n LLM node credentials (custom HTTP headers) custom headers in credentials for LLM sub-nodes (e.g., OpenAI/Anthropic/Lemonade) = avoid configuring custom headers; use alternative authentication mechanisms where possible - Compensating control
Restrict access to execution data to fully trusted users only, so only trusted users can read exposed header names/values and exported workflow execution records.
- Operational
Rotate any API keys or secrets that may have been stored as custom header values in affected credentials, because leaked values may remain accessible via persisted and exported execution data.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-65589?
CVE-2026-65589 has a medium severity level with a CVSS score of 5.1.
What is the impact of CVE-2026-65589?
CVE-2026-65589 allows credential exposure through plaintext execution data during workflow runs for certain LLM sub-nodes.
How do I fix CVE-2026-65589?
To mitigate CVE-2026-65589, update n8n to version 1.123.64 or later.
Who is affected by CVE-2026-65589?
Any authenticated users with access to the execution data of n8n workflows that use affected LLM sub-nodes are at risk.
What types of credentials are exposed in CVE-2026-65589?
CVE-2026-65589 exposes custom HTTP headers configured in credentials for specific LLM sub-nodes.