CVE-2026-72763 Overview
CVE-2026-72763 is an authorization flaw in n8n, an open-source workflow automation platform. The vulnerability affects n8n versions before 1.123.67, 2.31.5, and 2.32.1. It stems from incomplete credential-access validation in the Execute Sub-workflow node. n8n validates credential access only for a node's top-level credentials but not for credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. An Editor with access to a shared workflow can reference credential IDs they do not own, allowing credential use or exfiltration within the parent workflow's project context. The issue is tracked under CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
An authenticated Editor with knowledge of a target credential ID can bypass n8n's credential-sharing controls and use or exfiltrate secrets outside their permitted scope.
Affected Products
- n8n versions prior to 1.123.67
- n8n versions prior to 2.31.5
- n8n versions prior to 2.32.1
Discovery Timeline
- 2026-08-11 - CVE-2026-72763 published to NVD
- 2026-08-11 - Last updated in NVD database
Technical Details for CVE-2026-72763
Vulnerability Analysis
n8n enforces credential-access checks when a workflow node references a credential through its top-level credentials property. The check confirms that the invoking user or workflow project is authorized to use the referenced credential ID before saving and before execution.
The Execute Sub-workflow node accepts an inline workflow definition as JSON. Nested nodes inside that inline JSON also declare credential references, but n8n does not apply the same authorization check to those nested references. Save-time validation and runtime validation both pass. At execution, the sub-workflow resolves credentials using the parent workflow's project context, which may include credentials the attacker cannot otherwise access.
An Editor on a shared workflow can craft an Execute Sub-workflow node whose inline JSON references any credential ID they know. The sub-workflow then runs with that credential, enabling the attacker to invoke authenticated actions or exfiltrate the secret by routing it to an attacker-controlled endpoint.
Root Cause
The root cause is inconsistent enforcement of authorization checks across credential-reference paths. The permission model treats top-level and inline sub-workflow credential references differently, aligning with CWE-639 where access control depends on a user-supplied identifier without verifying ownership.
Attack Vector
Exploitation requires an authenticated account with Editor access to a shared workflow, and workflow sharing must be enabled on the instance. The attacker must also know or guess the target credential's ID. No user interaction is required. See the n8n GitHub Security Advisory GHSA-cj9h-qx8g-pq2g and the VulnCheck Advisory on n8n for additional technical detail.
Detection Methods for CVE-2026-72763
Indicators of Compromise
- Execute Sub-workflow nodes whose inline workflow JSON references credential IDs not owned or shared with the workflow's editor.
- Workflow executions that invoke credentials belonging to projects outside the parent workflow's declared sharing scope.
- Unexpected outbound HTTP requests from sub-workflow executions to unfamiliar destinations, especially requests carrying credential material or tokens.
Detection Strategies
- Audit stored workflows for Execute Sub-workflow nodes and enumerate every credential ID referenced inside inline nodes[] entries, then compare against sharing permissions.
- Correlate n8n execution logs with credential inventory to flag credentials used by editors who lack direct sharing rights.
- Review workflow modification history for recently added or edited Execute Sub-workflow nodes with inline JSON payloads.
Monitoring Recommendations
- Forward n8n audit and execution logs to a centralized SIEM and alert on credential use by non-owning users.
- Monitor egress traffic from n8n workers for anomalous destinations following sub-workflow executions.
- Track creation and modification of shared workflows and alert on inline sub-workflow definitions that reference credentials outside the current project.
How to Mitigate CVE-2026-72763
Immediate Actions Required
- Upgrade n8n to 1.123.67, 2.31.5, or 2.32.1 or later, matching your release train.
- Rotate any credentials that could have been referenced by editors of shared workflows on affected versions.
- Review shared workflows for unauthorized Execute Sub-workflow nodes and remove suspicious inline definitions.
Patch Information
The n8n maintainers released fixed builds in 1.123.67, 2.31.5, and 2.32.1. The patched versions apply credential-access validation to credentials referenced inside inline sub-workflow JSON at both save-time and runtime. Consult the n8n GitHub Security Advisory GHSA-cj9h-qx8g-pq2g for release notes and upgrade guidance.
Workarounds
- Disable workflow sharing on the instance until upgrades are applied, if operational needs allow.
- Restrict Editor role assignments on shared workflows and limit membership to trusted operators.
- Segment sensitive credentials into projects that do not overlap with shared-workflow editors, reducing the blast radius of any inline reference.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
