Skip to content
MediumVulnerabilityLLM-specific

GHSA-89gh-3pgc-v5h2: n8n: Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data

Published
Record updated
View JSON
Affected
  • n8n >= 2.0.0-rc.0, < 2.29.8, fixed in 2.29.8, released July 8, 2026, 14 days before disclosure
  • n8n >= 2.30.0, < 2.30.1, fixed in 2.30.1, released July 8, 2026, 14 days before disclosure
  • n8n < 1.123.64, fixed in 1.123.64, released July 8, 2026, 14 days before disclosure
Known exploitation
Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
EPSS
0.5%

Summary

Custom HTTP headers set in credentials for certain LLM sub-nodes, including OpenAI, Anthropic, and Lemonade, are masked in the n8n UI but written in plaintext into execution data. Any authenticated user with access to an affected workflow's execution data 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 a single execution.

Mitigation

Fixed in n8n versions 1.123.64, 2.29.8, and 2.30.1. Upgrade to one of these versions or later. If upgrading is not immediately possible, restrict execution data access to fully trusted users only, avoid configuring custom headers in LLM node credentials, and 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.