Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain editor access to shared workflow
-
DeliveryCreate node with duplicate ID and mismatched name
-
ExploitBypass credential tamper guard
-
ExecutionRetain victim credential, redirect host to attacker
-
ImpactWorkflow executes, secrets exfiltrated to attacker host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires an authenticated account with EDITOR access to a workflow that is SHARED with a higher-privileged victim (PR:L) - not available to anonymous or read-only users. The attacker must construct a node whose ID duplicates an existing node while the node name is mismatched, triggering the ID-versus-name matching flaw that bypasses the workflow credential tamper guard (the AT:P attack requirement). Realistic risk is therefore concentrated in multi-tenant or team deployments where low-privilege editors collaborate on shared workflows with credentials owned by others; single-user or fully-trusted-editor installations are effectively unaffected. Patched in n8n 1.123.80. |
| Impact | This is a moderate-risk, authenticated authorization flaw (CWE-639) rather than a top-priority emergency. The vendor-supplied CVSS 4.0 vector (5.8, AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N with subsequent-system SC:H/SI:H/SA:H) tells a consistent story: network-reachable but gated behind editor-level authentication (PR:L) and a specific exploitation precondition (AT:P - the attacker must craft duplicate node IDs that defeat the tamper guard). Direct confidentiality impact is only Low (VC:L), with the elevated subsequent-system metrics (SC:H/SI:H/SA:H) reflecting the harm of redirecting victim credentials to an attacker-controlled downstream host. There is NO EPSS score, NO CISA KEV listing, and NO public proof-of-concept provided, so this is 'no public exploit identified at time of analysis.' The signals do not conflict, but note the exploitation gate: it requires an existing editor account on a SHARED workflow, which bounds it to insider/multi-tenant abuse rather than mass internet exploitation. A patch is confirmed available (GHSA-7gjv-rcf8-x5qc, fixed in 1.123.80). Verdict: patch in normal cadence; prioritize if n8n is used in multi-tenant/shared-workflow deployments where low-privilege editors are not fully trusted. |
| Exploit ScenarioDerived | An attacker holding editor access to a workflow shared with a higher-privileged victim constructs a node whose ID collides with (duplicates) a legitimate node while using a mismatched name, defeating n8n's credential tamper guard. The guard fails to detect that the node now references the victim's stored credential, so the attacker retains that credential and rewrites the request target (e.g. host field) to an attacker-controlled endpoint, causing the victim's secrets to be transmitted to the attacker on the next execution. No public exploit code was identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Credential tampering in n8n versions before 1.123.80 lets an authenticated user with editor access to a shared workflow bypass the workflow credential tamper guard by constructing a node whose ID duplicates an existing node while its name does not match, allowing the attacker to retain the victim's credentials and redirect secrets to attacker-controlled hosts. Exploitation is not available to anonymous or read-only users: it requires editor privileges on a workflow shared with a higher-privileged credential owner, so realistic risk is concentrated in multi-tenant or team deployments where low-privilege editors collaborate on workflows containing credentials owned by others, while single-user or fully-trusted-editor installations are effectively unaffected. There is no public exploit identified at time of analysis, and the vendor has released a fix in n8n 1.123.80; this is a moderate-risk authenticated authorization flaw (CWE-639, vendor-assigned CVSS 5.8 with changed scope) rather than a top-priority emergency.
RemediationAI
Vendor-released patch: upgrade n8n to 1.123.80 or later, as documented in the GitHub advisory GHSA-7gjv-rcf8-x5qc and the VulnCheck advisory at https://www.vulncheck.com/advisories/n8n-before-1.123.80-credential-tampering-via-duplicate-node-ids. Until the upgrade can be staged, reduce the exposure by tightening the sharing model: restrict editor permissions on workflows that carry production, third-party, or otherwise high-value credentials so that only trusted operators can modify those nodes, and audit workflows for duplicate node IDs with mismatched names since such pairs are the exploit precondition. Isolating credentials into separate projects or dedicated n8n instances prevents an editor's node from reaching secrets owned by another user, at the cost of added operational overhead and duplicated workflow maintenance. Rotating any credentials that lived on workflows shared with untrusted editors is advisable if tampering is suspected, because secret redirection to attacker-controlled hosts is not detectable from within the workflow alone. Note that simply restricting read-only access is insufficient - the flaw is reachable by any authenticated editor, so the effective control is the reduction of editor rights themselves rather than the removal of anonymous access.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
n8n is a workflow automation platform in which workflows are composed of nodes that are referenced both by a node ID and a node name. The workflow credential tamper guard is intended to prevent a user from swapping, rebinding, or exfiltrating credentials attached to nodes they do not own; the guard performs a matching operation that can be confused when a node's ID duplicates an existing node but carries a mismatched name, so the ID-versus-name comparison resolves to the wrong node and the tamper check is skipped. The underlying weakness is CWE-639 (Authorization Bypass Through User-Controlled Key), i.e. the attacker controls a key (the node ID) that the authorization logic trusts without verifying uniqueness or binding it to the correct node identity. The affected package per CPE is cpe:2.3:a:n8n-io:n8n:*:*:*:*:*:*:*:*, covering all releases before 1.123.80. The CVSS 4.0 vector (CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H) reflects network attack, low complexity but a present attack requirement (AT:P, the crafted duplicate-ID/mismatched-name node), low privileges, no user interaction, and a scope change with high subsequent confidentiality, integrity, and availability impact on the credential-bearing component - matching an authorized editor subverting the credential boundary for data they were never entitled to handle.
Know when N8n gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H
Network-reachable but requires editor authentication (PR:L); scope change (S:C) since secrets are redirected to a separate attacker host; impact limited to low credential disclosure and credential-reference tampering (C:L/I:L, A:N).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
1DescriptionCVE.org
n8n versions before 1.123.80 contain a credential tampering vulnerability where duplicate node IDs bypass the workflow credential tamper guard. Attackers with editor access to shared workflows can exploit mismatched node ID and name matching to retain victim credentials and redirect secrets to attacker-controlled hosts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation
n8n workflow automation (through 1.121.2) allows authenticated users to execute arbitrary code via the n8n service, with
n8n workflow automation (1.65.0 to 1.121.0) allows unauthenticated file access through form-based workflows. A critical
n8n has a fifth critical RCE vulnerability (CVSS 9.9) in the Expression evaluator, enabling code execution through craft
Authenticated users who can create or modify an n8n workflow can achieve remote code execution on the n8n host by abusin
A prototype pollution vulnerability in the XML and GSuiteAdmin nodes of n8n workflow automation platform allows authenti
An authenticated user with workflow creation or modification privileges in n8n workflow automation platform can exploit
n8n-workflows Main Commit ee25413 allows attackers to execute a directory traversal via the download_workflow function w
Authenticated n8n users can hijack administrator accounts when LDAP authentication is enabled by manipulating their LDAP
The n8n package 0.218.0 for Node.js allows Escalation of Privileges. Rated high severity (CVSS 8.8), this vulnerability
SQL injection in n8n's Data Table Get node allows authenticated users with workflow modification permissions to execute
Authenticated users can exploit string formatting and exception handling in n8n's Python task executor to escape sandbox
EUVD-2026-90751
GHSA-v9vf-c827-9m93
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB