Skip to content
n8nGHSA-89gh-3pgc-v5h2

n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data

MediumCVE-2026-65589 · Published Jul 22, 2026

## 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 ...

GitHub advisory

Affected versions

PackageAffectedFixed in
n8n
npm
< 1.123.641.123.64
>= 2.30.0, < 2.30.12.30.1
>= 2.0.0-rc.0, < 2.29.82.29.8
Details and references

## 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.

CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:L/SA:N
Severity from
GitHub (reviewed advisory)
Weakness
CWE-532
Also known as
CVE-2026-65589

More n8n advisories

All n8n
Advisory
n8n: Snowflake Node executeQuery Operation Allows SQL Injection via Unparameterized Expression Interpolation
MediumJul 22
n8n: SQL injection
MediumJul 22
n8n: Cross-Tenant Module-Cache Poisoning in the JS Task Runner
MediumJul 22
n8n: Unauthenticated Endpoint Allows Cancellation of Any User's Active Test Webhook
MediumJul 22
n8n: GraphQL Node Bypasses "Allowed HTTP Request Domains" Restriction
MediumJul 22
n8n: improper authorization
MediumJul 22

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.