n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data
CVE-2026-65589 · GHSA-89gh-3pgc-v5h2 · published 2026-07-22
- Severity
- Medium
- CVSS score
- 5.1
- Chance of exploitation (EPSS)
- 0.48%
- Fixed in
- 2.30.1
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
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.
Upgrade n8n to 2.30.1 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
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.
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.
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- HighWorkspace dotenv files could override provider credentialsopenclaw
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.