INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-72763

n8n: Shared-Workflow Editor Can Exfiltrate Credentials via Inline Sub-Workflow JSON

CVE-2026-72763 ยท 2026-07-22 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Authentication and access control
Affected
n8n (npm)
Gets past
Authorisation check
CVSS
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:L
EPSS
0.4% chance of exploitation in 30 days

How it works, in short

Credential checks inspect only top-level node credentials, so an editor can reference other credentials inside a sub-workflow's inline JSON and use them. (Our summary, written by a model. The source text is below.)

Details

Impact

n8n's credential-access checks validated only a node's top-level credentials, not credentials referenced inside an Execute Sub-workflow node's inline workflow JSON. A member with editor access to a shared workflow could reference a credential they were not permitted to use inside that inline JSON; it passed both save-time and runtime validation and resolved in the parent workflow's project context, letting the member use or exfiltrate a credential they could not otherwise access.

Exploitation requires workflow sharing to be enabled and the attacker to have been explicitly granted Editor access to a shared workflow. The attacker must also know the target credential's ID.

Patches

The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:
- Restrict workflow sharing to fully trusted users only, and avoid granting Editor access to untrusted members on workflows that use sensitive credentials.
- Audit shared workflows for Execute Sub-workflow nodes with Source = "Parameter" and review their inline workflow definitions for unexpected credential references.
- Restrict network egress from the n8n instance to prevent connections to attacker-controlled endpoints.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

References

Source: GitHub Advisory Database, used under CC BY 4.0.