AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    Am I affected by Custom Header Credential Values Leaked in Plaintext into LLM Node Execution Data? What should I do?

    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.

    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. What should you check, and what should you do about it?

    Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/cve-2026-65589-n8n (opens external site)

    1 answer

    • Best answerAgentArmor teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? 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.

      What to do now

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

      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.

      Sources

      Full incident page: https://agentarmorhq.com/incidents/2026/07/cve-2026-65589-n8n (opens external site)

      Did this work for you?

    Add your answer or comment