n8n: Credential Exfiltration via Permission Bypass
Description
A member-level user with editor access to a shared workflow in n8n can access credentials they do not own via public API endpoints due to incomplete ownership checks.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A member-level user with editor access to a shared workflow in n8n can access credentials they do not own via public API endpoints due to incomplete ownership checks.
Vulnerability
A credential ownership check bypass exists in n8n when a member-level user with editor access to a shared workflow uses specific public API endpoints. The vulnerability affects instances where workflow sharing is enabled and at least one workflow has been shared with a member-level user as an Editor. Affected versions are all n8n releases prior to 1.123.55, 2.25.7, and 2.26.2 [1][2].
Exploitation
An attacker must have a member-level account with editor permissions on a shared workflow. By calling the vulnerable public API endpoints, the attacker can reference credentials that belong to other users without proper ownership verification [1][2].
Impact
Successful exploitation allows the attacker to exfiltrate credentials they do not own, leading to unauthorized access to sensitive data and potential compromise of integrated services. The CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N, indicating high confidentiality and integrity impact with a network attack vector [1][2].
Mitigation
The issue is fixed in n8n versions 1.123.55, 2.25.7, and 2.26.2. Users should upgrade to one of these versions or later. If immediate upgrade is not possible, administrators can restrict workflow sharing to fully trusted users and audit shared workflows for unexpected credential references as temporary workarounds [1][2].
AI Insight generated on Jun 16, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
1- n8n: 16 CVEs Disclosed in Single Batch — Credential Leaks, Prototype Pollution, and Sandbox EscapeVypr Intelligence · Jun 16, 2026