Medium (AgentArmorHQ estimate)Data leak

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

Product
n8n
CVE
CVE-2026-65589
Affected
npm/n8n affected < 1.123.64; npm/n8n affected >= 2.0.0-rc.0, < 2.29.8; npm/n8n affected >= 2.30.0, < 2.30.1
Fixed in
1.123.64

Last verified against sources: October 26, 2026

Am I affected?

n8n: affected npm/n8n affected < 1.123.64; npm/n8n affected >= 2.0.0-rc.0, < 2.29.8; npm/n8n affected >= 2.30.0, < 2.30.1. Fixed in 1.123.64.

  • Check your version: run npm ls n8n. Versions < 1.123.64 of n8n are affected. [1]

What to do now

  1. Upgrade to the fixed version: run npm install n8n@1.123.64 (first patched version 1.123.64). [1]
  2. Upgrade to one of these versions or later to remediate the vulnerability. [1]
  3. Restrict access to execution data to fully trusted users only. [1]
  4. Avoid configuring custom headers in LLM node credentials; use alternative authentication mechanisms where possible. [1]
  5. Rotate any API keys or secrets that may have been stored as custom header values in affected credentials. [1]

General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.

Discuss this incident

What happened

  • 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. [1]

Impact

  • 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. [1]
  • Leaked values may remain accessible beyond the lifetime of a single execution. [1]

What was done

  • The issue has been fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. [1]
  • Users should upgrade to one of these versions or later to remediate the vulnerability. [1]

Sources

  1. GHSA-89gh-3pgc-v5h2 — GitHub Advisory Database

Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.

Share advisory brief with your team

Copy a plain-text summary for Slack, GitHub issues, or team security channels.

Brief
[CVE-2026-65589] Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data
Product: n8n | Affected: npm/n8n affected < 1.123.64; npm/n8n affected >= 2.0.0-rc.0, < 2.29.8; npm/n8n affected >= 2.30.0, < 2.30.1 | Fixed in: 1.123.64
Summary: 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.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/07/cve-2026-65589-n8n
Was this page useful?

Corrections

Report an error or request a correction. We review requests within 5 business days and add a dated correction note.

10 to 2,000 characters. A link to a source helps. Stored as plain text.

Discussions for CVE-2026-65589

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Check before you install

Paste a package name or a GitHub link and get a clear answer in seconds: Block, Review or No known issues. No account needed.

Check a package

Questions? Contact us