CVE-2026-103256: n8n: Wekan/Baserow credential leak to arbitrary hosts
HIGHn8n versions before 2.39.6 (and 2.40.0 before 2.40.1) send Wekan and Baserow username-and-password credentials, unencrypted, to whatever host is set in the credential's host field, with no domain validation. Anyone with permission to edit a credential can point that host at a server they control and capture the account password when a workflow uses it. Urgency is moderate: EPSS is low (0.00211, though the percentile is high), there is no public exploit, no Nuclei template, it is not in CISA KEV, and CISA SSVC says TRACK. The impact is still real because n8n is a hub for AI agent workflows, and the scope change (S:C) means a leaked password gives access to other systems, such as the Wekan and Baserow instances. Upgrade to n8n 2.39.6, 2.40.1 or later. Until then, restrict who can edit credentials and audit recent changes to Wekan and Baserow credential host fields. Rotate any passwords that may have been exposed.
What is the risk?
Medium-to-high risk, driven by impact rather than likelihood. CVSS 7.1 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N) reflects network reach, low required privileges and a scope change, offset by high complexity because the attacker needs credential-edit rights and a workflow must run with the modified credential. Exploitation likelihood is low: EPSS 0.00211, no public exploit, no scanner template, not in KEV, SSVC TRACK. Multi-user n8n deployments with broad credential-edit permissions are the most exposed. The package has a high count of past CVEs (244 in the same package) and an OpenSSF Scorecard of 6.7/10, which points to a recurring flow of security issues.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| n8n | npm | — | No patch |
Do you use n8n? You're affected.
How severe is it?
What is the attack surface?
What should I do?
6 stepsUpgrade n8n to 2.39.6 or later on the 2.39 line, or to 2.40.1 or later on the 2.40 line.
Limit credential update permissions to a minimal set of trusted users and review project/role sharing of credentials.
Audit the host fields of all Wekan and Baserow credentials against the expected instance URLs and look for unexpected external hosts.
Rotate Wekan and Baserow passwords used in n8n if any credential was modified or the host is unexpected. Prefer API tokens or service accounts with least privilege.
Detection: monitor egress from the n8n host for connections to unknown destinations after Wekan/Baserow node executions, and review n8n audit logs for credential edits.
Consider egress allowlisting for the n8n server.
What does CISA's SSVC say?
Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-103256?
n8n versions before 2.39.6 (and 2.40.0 before 2.40.1) send Wekan and Baserow username-and-password credentials, unencrypted, to whatever host is set in the credential's host field, with no domain validation. Anyone with permission to edit a credential can point that host at a server they control and capture the account password when a workflow uses it. Urgency is moderate: EPSS is low (0.00211, though the percentile is high), there is no public exploit, no Nuclei template, it is not in CISA KEV, and CISA SSVC says TRACK. The impact is still real because n8n is a hub for AI agent workflows, and the scope change (S:C) means a leaked password gives access to other systems, such as the Wekan and Baserow instances. Upgrade to n8n 2.39.6, 2.40.1 or later. Until then, restrict who can edit credentials and audit recent changes to Wekan and Baserow credential host fields. Rotate any passwords that may have been exposed.
Is CVE-2026-103256 actively exploited?
No confirmed active exploitation of CVE-2026-103256 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-103256?
1. Upgrade n8n to 2.39.6 or later on the 2.39 line, or to 2.40.1 or later on the 2.40 line. 2. Limit credential update permissions to a minimal set of trusted users and review project/role sharing of credentials. 3. Audit the host fields of all Wekan and Baserow credentials against the expected instance URLs and look for unexpected external hosts. 4. Rotate Wekan and Baserow passwords used in n8n if any credential was modified or the host is unexpected. Prefer API tokens or service accounts with least privilege. 5. Detection: monitor egress from the n8n host for connections to unknown destinations after Wekan/Baserow node executions, and review n8n audit logs for credential edits. 6. Consider egress allowlisting for the n8n server.
What systems are affected by CVE-2026-103256?
This vulnerability affects the following AI/ML architecture patterns: agent frameworks, workflow automation, AI agent orchestration, data pipelines.
What is the CVSS score for CVE-2026-103256?
CVE-2026-103256 has a CVSS v3.1 base score of 7.1 (HIGH). The EPSS exploitation probability is 0.21%.
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0012Valid AccountsAML.T0055Unsecured CredentialsAML.T0098AI Agent Tool Credential HarvestingCompliance Controls Affected
What are the technical details?
Original Advisory
n8n versions before 2.39.6 and 2.40.0 before 2.40.1 contain a credentials leak vulnerability in the Wekan and Baserow username-and-password credentials that sends unencrypted passwords to unvalidated hosts. Attackers with credential update permissions can modify the host field to receive account passwords at arbitrary hosts, bypassing domain validation controls.
Exploitation Scenario
An attacker with a low-privilege n8n account that can edit a shared credential, such as a malicious insider or a compromised contributor account, changes the host field of an existing Baserow credential to an attacker-controlled server. When a scheduled workflow, perhaps one feeding data to an AI agent, executes the Baserow node, n8n sends the username and password in the pre-authentication request to the attacker's host. The attacker logs the plaintext password, then signs in to the real Baserow or Wekan instance to read or alter data, and may reuse the password elsewhere.
Weaknesses (CWE)
CWE-522 — Insufficiently Protected Credentials: The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
- [Architecture and Design] Use an appropriate security mechanism to protect the credentials.
- [Architecture and Design] Make appropriate use of cryptography to protect the credentials.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:NReferences
Timeline
Related Vulnerabilities
CVE-2026-3366310.0n8n: member role steals plaintext HTTP credentials
Same package: n8nCVE-2026-3366010.0TensorFlow: type confusion NPD in tensor conversion
Same package: n8nCVE-2026-2185810.0n8n: Input Validation flaw enables exploitation
Same package: n8nCVE-2026-275779.9n8n: Code Injection enables RCE
Same package: n8nCVE-2026-274949.9n8n: security flaw enables exploitation
Same package: n8n