Summary
A broken access control issue in n8n allows member-level users with editor rights on shared workflows to reference credentials they do not own through certain public API endpoints.
When workflow sharing is enabled, this can expose cross-user credentials and sensitive integrations to unauthorized workflow editors.
Affected context
This vulnerability occurs in n8n instances that enable workflow sharing and allow member-level users to act as Editors on shared workflows.
In this context, the platform partially enforces credential ownership checks, creating gaps when credentials are referenced via specific public API endpoints rather than the primary UI flows.
The issue is limited to environments where workflows and credentials are shared among multiple users, and where editors can modify or configure nodes that use stored credentials.
Exploit preconditions
- Attack surface: n8n public API endpoints used for workflow configuration and credential referencing.
- Required access: Member-level account with editor permissions on at least one shared workflow.
- Trigger point: Editing or configuring workflow nodes or related resources in ways that reference credentials owned by other users via exposed endpoints.
- Why exploitation is possible: Credential ownership validation is applied inconsistently across API paths, allowing credential IDs belonging to other users to be referenced without a complete authorization check.
Why this happens
The root cause lies in incomplete and inconsistent authorization logic for credential usage within shared workflows.
While n8n enforces ownership checks in some layers, certain public API endpoints lack full validation to ensure that the requesting user actually owns or is explicitly permitted to use the requested credentials.
This maps to CWE-863: Incorrect Authorization, where privilege checks are missing or incorrectly implemented, allowing users with legitimate access to one resource (a shared workflow) to access another resource (other users' credentials) beyond their intended permissions.
Potential impact
- Member-level users may access credentials owned by other users.
- Workflows edited by unauthorized users could interact with external systems (APIs, databases, SaaS services) using stolen credentials.
- Sensitive data from connected services can be exposed or exfiltrated through modified workflows.
- External integrations may be misused for unauthorized actions, such as sending messages, triggering operations, or modifying data.
- Credential trust boundaries within the automation environment can be weakened, leading to broader organizational data exposure.
General mitigation guidance
Effective mitigation focuses on enforcing robust authorization checks on every path where credentials can be referenced or used.
Common secure patterns include:
- Centralizing access control logic so that all credential-related operations pass through a single, well-tested authorization layer.
- Binding credentials explicitly to owners or groups and verifying this binding on every API call that reads, references, or executes with those credentials.
- Reducing implicit trust in workflow editors by limiting what shared workflows can do with credentials they do not explicitly own or are not explicitly granted.
- Applying least-privilege to role definitions so that editor-level users cannot expand their effective access by manipulating identifiers or API parameters.
- Designing workflows and credential stores so that cross-tenant or cross-user access requires explicit grant, not mere knowledge of an identifier.
How teams detect issues like this
Detection strategies typically center on reviewing access control implementations and monitoring credential usage patterns:
- Static analysis or manual code review to identify API endpoints that perform credential operations without consistent authorization checks.
- Policy-based tests ensuring that every credential-related route enforces ownership or permission checks before returning data or executing actions.
- Audit logging of credential access and workflow executions, with alerts for credentials being used by accounts other than their owners or designated groups.
- Automated security tests or integration tests that attempt to reference credentials from non-owning accounts to confirm that authorization rules are applied uniformly.

