Advisoriesby Ibisn8n: insecure direct object reference
Impact
An authenticated user with the global:member role could exploit chained authorization flaws in n8n's credential pipeline to steal plaintext secrets from generic HTTP credentials (httpBasicAuth, httpHeaderAuth, httpQueryAuth) belonging to other users on the same instance.
The attack abuses a name-based credential resolution path that does not enforce ownership or project scope, combined with a bypass in the credentials permission checker that causes generic HTTP credential types to be skipped during pre-execution validation. Together, these flaws allow a member-role user to resolve another user's credential ID and execute a workflow that decrypts and uses that credential without authorization.
Native integration credential types (e.g. slackApi, openAiApi, postgres) are not affected by this issue.
This vulnerability affects Community Edition only. Enterprise Edition has additional permission gates on workflow creation and execution that independently block this attack chain.
Patches
The issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.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 instance access to fully trusted users only.
- Audit credentials stored on...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| n8n npm | < 1.123.27 | 1.123.27 |
| >= 2.14.0, < 2.14.1 | 2.14.1 | |
| >= 2.0.0-rc.0, < 2.13.3 | 2.13.3 |
Details and references
## Impact An authenticated user with the `global:member` role could exploit chained authorization flaws in n8n's credential pipeline to steal plaintext secrets from generic HTTP credentials (`httpBasicAuth`, `httpHeaderAuth`, `httpQueryAuth`) belonging to other users on the same instance. The attack abuses a name-based credential resolution path that does not enforce ownership or project scope, combined with a bypass in the credentials permission checker that causes generic HTTP credential types to be skipped during pre-execution validation. Together, these flaws allow a member-role user to resolve another user's credential ID and execute a workflow that decrypts and uses that credential without authorization. Native integration credential types (e.g. `slackApi`, `openAiApi`, `postgres`) are not affected by this issue. This vulnerability affects Community Edition only. Enterprise Edition has additional permission gates on workflow creation and execution that independently block this attack chain. ## Patches The issue has been fixed in n8n versions 1.123.27, 2.13.3, and 2.14.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 instance access to fully trusted users only. - Audit credentials stored on the instance and rotate any generic HTTP credentials (`httpBasicAuth`, `httpHeaderAuth`, `httpQueryAuth`) that may have been exposed. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-639
- Also known as
- CVE-2026-33663
More n8n advisories
All n8n
n8n's Source Control SSH Configuration Uses StrictHostKeyChecking=noCVE-2026-33724fixed in 2.5.0n8n Has External Secrets Authorization Bypass in Credential SavingCVE-2026-33722fixed in 1.123.23 +1n8n Has Authorization Bypass in OAuth Callback via N8N_SKIP_AUTH_ON_OAUTH_CALLBACKCVE-2026-33720fixed in 2.8.0n8n: LDAP Email-Based Account Linking Allows Privilege Escalation and Account TakeoverCVE-2026-33665fixed in 1.121.0 +1n8n has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL ModeCVE-2026-33660fixed in 1.123.27 +2n8n has In-Process Memory Disclosure in its Task RunnerCVE-2026-27496fixed in 1.123.22 +2