Credential disclosure via unmasked LLM custom headers
Published Jul 22, 2026 · Updated Jul 22, 2026
Credential exposure in n8n 1.x before 1.123.64, 2.29.x before 2.29.8, and 2.30.0 allows remote authenticated users to read LLM header secrets. During workflow runs, affected LLM sub-nodes copy custom HTTP credential header names and values into execution data without applying the masking used by the interface. Exposure requires a workflow that uses custom headers and access to its execution data; persisted database records and exports retain the API keys or other secrets.
Summary
What happened
Credential exposure in n8n 1.x before 1.123.64, 2.29.x before 2.29.8, and 2.30.0 allows remote authenticated users to read LLM header secrets. During workflow runs, affected LLM sub-nodes copy custom HTTP credential header names and values into execution data without applying the masking used by the interface. Exposure requires a workflow that uses custom headers and access to its execution data; persisted database records and exports retain the API keys or other secrets.
The record
- CVE
- CVE-2026-65589
- Published
- Jul 22, 2026
- Updated
- Jul 22, 2026
- Vendor
- n8n
- Product
- n8n
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 22, 2026CVE publishedPublication date reported by the CVE source.
- Jul 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.123.64
- Affected versionversion=0 <2.29.8
- Affected versionversion=0 <2.30.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo