EUVD-2026-101736
GHSA-9mgf-2q6c-j3gw
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged member
-
DeliveryCraft Execute Sub-workflow in inline JSON mode
-
ExploitSupply trusted foreign workflow identifier
-
ExecutionBypass project ownership check
-
ImpactResolve cross-project credentials and modify static data
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 n8n member account (PR:L) on an instance where the Execute Sub-workflow node is used in inline JSON mode, and the attacker must supply a trusted workflow identifier referencing a project they do not belong to. The attack requirement (AT:P) and the multi-project dependency are the key limiting factors: single-tenant or single-project deployments, and instances not using the inline JSON sub-workflow path, are materially less exposed. There is no unauthenticated or default-configuration remote path - the attacker must already hold valid low-privilege credentials and target a known foreign workflow identifier. |
| Impact | This is a moderate, authenticated-access vulnerability rather than a mass-exploitation emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:L/UI:N) confirms a network-reachable flaw but requires an authenticated low-privileged member (PR:L) and carries an attack requirement (AT:P), meaning exploitation depends on a specific condition - here, use of the Execute Sub-workflow inline JSON mode. Impact is skewed toward confidentiality: VC:H and SC:H reflect that an attacker can resolve and read credentials belonging to projects they do not own (a cross-tenant/cross-project boundary break), while integrity is only partial (VI:L/SI:L - modifying another workflow's static data and error-workflow dispatch) and there is no availability impact (VA:N). No EPSS score, KEV listing, or POC is present in the supplied data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The signals are consistent rather than conflicting: a genuine authorization/IDOR weakness (CWE-639) that matters most in multi-tenant n8n deployments with untrusted or semi-trusted members, but the authentication requirement and the specialized feature path limit its real-world blast radius. Priority should be driven by whether the instance hosts multiple projects/tenants sharing one n8n installation. |
| Exploit ScenarioDerived | A low-privileged but authenticated member of one n8n project creates a workflow using the Execute Sub-workflow node in inline JSON mode and supplies a trusted workflow identifier belonging to a project they are not a member of. Because the identifier is trusted without an ownership check, n8n resolves credentials from that foreign project and lets the attacker read them and tamper with the targeted workflow's static data and error-workflow dispatch. No public proof-of-concept is identified in the provided data, but the attack requires only legitimate low-level access and knowledge of a target workflow identifier. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Authorization bypass in n8n versions before 1.123.83 allows an authenticated member account to spoof workflow identity by supplying a trusted workflow identifier in the Execute Sub-workflow node's inline JSON mode, enabling credential resolution from projects the attacker does not belong to and unauthorized modification of another workflow's static data and error-workflow dispatch. The vulnerability (CWE-639, authorization bypass through user-controlled key) requires valid low-privilege credentials plus knowledge of a foreign workflow identifier, so single-tenant, single-project, or non-inline-JSON deployments are materially less exposed. No public exploit code or confirmed active exploitation was identified at time of analysis, and the independent assessment rates this as a moderate, authenticated-access issue rather than a mass-exploitation emergency.
RemediationAI
Upgrade n8n to version 1.123.83 or later, which is the vendor-released fix for this authorization bypass (reference: https://github.com/n8n-io/n8n/security/advisories/GHSA-866p-xg8v-g2q7). Where immediate upgrade is not possible, the most effective compensating control is to remove reliance on the vulnerable path: audit and, if feasible, disable or restrict the Execute Sub-workflow node when configured in inline JSON mode, noting that this breaks legitimate orchestration workflows that depend on it. Second, enforce strict project isolation so that no member account can enumerate or guess workflow identifiers outside its own project, or temporarily reduce the member role to a narrower custom role that cannot create or edit sub-workflow nodes, accepting the loss of legitimate automation capability. Third, review static data and error-workflow dispatch configuration for unexpected cross-project modifications, rotate credentials belonging to any project whose ID may have been referenced by an untrusted user, and monitor workflow executions for sub-workflow calls that resolve into projects the triggering user does not belong to. Deployments that operate as a single project, or that do not use inline JSON sub-workflows, are less exposed and can prioritize remediation accordingly.
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 where workflows, credentials, and static data are scoped to projects, and users are assigned roles such as member. The Execute Sub-workflow node allows one workflow to invoke another; in its inline JSON mode, the caller supplies parameters as free-form JSON, including a workflow identifier field that the platform treats as trusted. CWE-639 describes exactly this class of defect: an authorization decision keyed on a user-controlled identifier without verifying that the requesting principal actually has access to the referenced object. Because the external key is not re-validated against the caller's project membership, a member can point the node at a workflow in a foreign project, causing credential lookup to resolve secrets belonging to that project and allowing writes to that workflow's static data and its error-workflow dispatch configuration. The assessed CVSS:3.1 vector AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N reflects remote reachability, high attack complexity driven by the need to know a valid foreign workflow ID, low privileges required, a scope change, high confidentiality impact from cross-project credential exposure, and limited integrity impact. Confidence in exploitation success is constrained by the AT:P attack-requirement signal in the vendor's CVSS 4.0 vector and by the multi-project prerequisite.
Know when the next one hits your stack
- 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:H/VI:L/VA:N/SC:H/SI:L/SA:N
Authenticated member access gives PR:L; the AT:P attack requirement maps to AC:H; the cross-project boundary break justifies S:C with C:H and only partial integrity (I:L), no availability impact.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
2DescriptionCVE.org
n8n before 1.123.83 contains an authorization bypass vulnerability that allows authenticated members to spoof workflow identity by supplying a trusted identifier in Execute Sub-workflow inline JSON mode. Attackers can set this identifier to resolve credentials from projects they do not belong to and modify another workflow's static data and error-workflow dispatch.
Technical POC Analysis
Evidence note: the supplied evidence is the GitHub advisory only.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
n8n automation deployments prior to 1.123.83 are affected by an authorization bypass that can allow a member-level user to cross project boundaries, resolve credentials from unrelated projects, and modify other workflows' static data or error handling. Organizations with multi-project or multi-tenant n8n environments and member accounts are most exposed, because automation workflows often hold sensitive credentials and business logic. No public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, so leadership should prioritize access restrictions and monitoring while treating the issue as a moderate, member-access risk rather than a mass-exploitation emergency.
No vendor-released patch identified at time of analysis. Restrict or disable the Execute Sub-workflow node's inline JSON mode, remove or limit member accounts, enforce strict project isolation, rotate credentials that may have been exposed, monitor for unauthorized cross-project workflow identifier use, and audit static data and error-workflow dispatch configurations.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Exploit-DB