n8n
Affected
- introduced
0, fixed1.123.27(semver)
Fixed versions
1.123.27
Fix
- Fixed version
1.123.27npm install [email protected]
Advisory
Also known as: CVE-2026-33663
n8n is Vulnerable to Credential Theft via Name-Based Resolution and Permission Checker Bypass in Community Edition
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:
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.
High Basis: The source's own band: HIGH
0, fixed 1.123.27 (semver)1.123.27
1.123.27npm install [email protected]2.14.0, fixed 2.14.1 (semver)2.14.1
2.14.1npm install [email protected]2.0.0-rc.0, fixed 2.13.3 (semver)2.13.3
2.13.3npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0