Skip to main content

n8n CVE-2026-65589

| EUVDEUVD-2026-47633 MEDIUM
Insertion of Sensitive Information into Log File (CWE-532)
5.1
CVSS 4.0 · Vendor: VulnCheck
Share

Severity by source

Vendor (VulnCheck) PRIMARY
5.1 MEDIUM
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
7.7 HIGH

PR:L because authenticated access is required; S:C and C:H reflect high-impact credential theft enabling access to downstream systems.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

2
Patch available
Jul 22, 2026 - 13:02 EUVD
Analysis Generated
Jul 22, 2026 - 12:30 vuln.today

DescriptionCVE.org

n8n versions before 1.123.64 fail to properly mask custom HTTP header credentials in LLM sub-node execution data, writing plaintext API keys and secrets to workflow execution records. Authenticated users with access to execution data can read exposed header values and credentials that persist in the database and can be exported.

AnalysisAI

Credential exposure in n8n's LLM sub-node allows authenticated users to read plaintext API keys and secrets persisted in workflow execution records. Versions before 1.123.64 fail to mask custom HTTP header values - such as Authorization or X-API-Key headers - when those headers are used in LLM node configurations, causing secrets to be written in cleartext to execution data stored in the database. While exploitation requires a low-privilege authenticated session, the downstream impact is high because recovered credentials can be used to access external APIs and services configured in those workflows. No public exploit code or KEV listing has been identified at time of analysis.

Technical ContextAI

n8n is an open-source, self-hostable workflow automation platform (cpe:2.3:a:n8n-io:n8n). It supports LLM sub-nodes that interact with AI APIs by constructing HTTP requests, including custom header configurations for authentication. The root cause is CWE-532 (Insertion of Sensitive Information into Log File / Execution Data), where the platform's credential masking logic fails to sanitize header values before persisting execution records. Unlike credential fields that n8n explicitly marks as sensitive and masks in the UI, custom HTTP headers in LLM node configurations are treated as generic parameters, so their values flow unredacted into execution records that are stored in the backend database and potentially exportable. The CVSS 4.0 AT:P (Attack Requirements: Present) reflects that exploitation depends on workflows being configured with LLM nodes using custom HTTP headers containing secrets - a common pattern when integrating third-party AI APIs requiring bearer tokens or API keys.

RemediationAI

Upgrade to n8n version 1.123.64 or later, which introduces proper masking of custom HTTP header values in LLM node execution data. The vendor-released patch is documented in the GitHub security advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-89gh-3pgc-v5h2. As a compensating control prior to patching, restrict access to execution data to only the minimum set of users who require it - n8n's role-based access controls should be audited to ensure low-trust users cannot read execution records from workflows containing LLM nodes. Additionally, rotate any API keys or secrets that may have been passed as custom HTTP headers in LLM nodes on affected versions, as those values should be considered compromised if any other authenticated user had access to execution history. Avoid storing long-lived credentials in header configurations; prefer short-lived tokens or API keys scoped to minimum permissions.

More in N8n

View all
CVE-2026-21877 CRITICAL POC
9.9 Jan 08

n8n workflow automation (through 1.121.2) allows authenticated users to execute arbitrary code via the n8n service, with

CVE-2026-21858 CRITICAL POC
10.0 Jan 08

n8n workflow automation (1.65.0 to 1.121.0) allows unauthenticated file access through form-based workflows. A critical

CVE-2026-1470 CRITICAL POC
9.9 Jan 27

n8n has a fifth critical RCE vulnerability (CVSS 9.9) in the Expression evaluator, enabling code execution through craft

CVE-2026-33660 CRITICAL POC
9.4 Mar 25

An authenticated user with workflow creation or modification privileges in n8n workflow automation platform can exploit

CVE-2026-33665 HIGH POC
8.8 Mar 25

Authenticated n8n users can hijack administrator accounts when LDAP authentication is enabled by manipulating their LDAP

CVE-2023-27563 HIGH POC
8.8 May 10

The n8n package 0.218.0 for Node.js allows Escalation of Privileges. Rated high severity (CVSS 8.8), this vulnerability

CVE-2026-0863 HIGH POC
8.5 Jan 18

Authenticated users can exploit string formatting and exception handling in n8n's Python task executor to escape sandbox

CVE-2023-27564 HIGH POC
7.5 May 10

The n8n package 0.218.0 for Node.js allows Information Disclosure. Rated high severity (CVSS 7.5), this vulnerability is

CVE-2023-27562 MEDIUM POC
6.5 May 10

The n8n package 0.218.0 for Node.js allows Directory Traversal. Rated medium severity (CVSS 6.5), this vulnerability is

CVE-2026-33724 MEDIUM POC
6.3 Mar 25

n8n versions prior to 2.5.0 contain a critical SSH host key verification bypass in the Source Control feature that allow

CVE-2026-33720 MEDIUM POC
6.3 Mar 25

This vulnerability in n8n (an open-source workflow automation platform) is an authentication bypass in the OAuth callbac

CVE-2026-27495 CRITICAL
9.9 Feb 25

Code injection in n8n workflow automation before 2.10.1/2.9.3/1.123.22 allows authenticated users to execute arbitrary c

Share

CVE-2026-65589 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy