CVE-2026-72763: Authorization Bypass Through User-Controlled Key in n8n-io n8n
n8n before 1.123.67, 2.31.5, and 2.32.1 validates credential-access only for a node's top-level credentials and not for credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. A member with Editor access to a shared workflow (when workflow sharing is enabled) who knows a target credential's ID can reference that credential in the inline JSON; it passes save-time and runtime validation and resolves in the parent workflow's project context, allowing the attacker to use or exfiltrate credentials they are not permitted to access.
AI Analysis
Technical Summary
The vulnerability exists because n8n does not validate credential access for credentials referenced inside an Execute Sub-workflow node's inline workflow JSON, only for top-level credentials. An Editor-level user who knows a credential ID can embed that credential in the inline JSON of a sub-workflow, bypassing save-time and runtime validation. This causes the credential to resolve in the parent workflow's project context, granting unauthorized access to credentials. This affects n8n versions prior to 1.123.67, 2.31.5, and 2.32.1.
Potential Impact
An attacker with Editor access to a shared workflow can leverage this vulnerability to access or exfiltrate credentials they are not authorized to use. This could lead to unauthorized actions or data exposure within the affected n8n instance. The CVSS 4.0 score of 7.2 reflects a high severity with network attack vector, low attack complexity, and partial privileges required.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Editor access to trusted users only and avoid sharing workflows that contain sensitive credentials. Monitor vendor channels for updates regarding patches or official mitigations.
CVE-2026-72763: Authorization Bypass Through User-Controlled Key in n8n-io n8n
Description
n8n before 1.123.67, 2.31.5, and 2.32.1 validates credential-access only for a node's top-level credentials and not for credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. A member with Editor access to a shared workflow (when workflow sharing is enabled) who knows a target credential's ID can reference that credential in the inline JSON; it passes save-time and runtime validation and resolves in the parent workflow's project context, allowing the attacker to use or exfiltrate credentials they are not permitted to access.
CVSS v4.0
Score 7.2high
Affected software
pkg:github/n8n-io/n8nRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability exists because n8n does not validate credential access for credentials referenced inside an Execute Sub-workflow node's inline workflow JSON, only for top-level credentials. An Editor-level user who knows a credential ID can embed that credential in the inline JSON of a sub-workflow, bypassing save-time and runtime validation. This causes the credential to resolve in the parent workflow's project context, granting unauthorized access to credentials. This affects n8n versions prior to 1.123.67, 2.31.5, and 2.32.1.
Potential Impact
An attacker with Editor access to a shared workflow can leverage this vulnerability to access or exfiltrate credentials they are not authorized to use. This could lead to unauthorized actions or data exposure within the affected n8n instance. The CVSS 4.0 score of 7.2 reflects a high severity with network attack vector, low attack complexity, and partial privileges required.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Editor access to trusted users only and avoid sharing workflows that contain sensitive credentials. Monitor vendor channels for updates regarding patches or official mitigations.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-10T15:06:16.417Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7b1519bf8831d539b28a55
Added to database: 08/11/2026, 12:27:05 UTC
Last enriched: 08/11/2026, 12:43:36 UTC
Last updated: 08/12/2026, 03:25:48 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.