CVE-2026-33663
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedn8n is an open source workflow automation platform. Prior to versions 2.14.1, 2.13.3, and 1.123.27, 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. 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. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Restrict instance access to fully trusted users only, and/or 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn authenticated user with global:member role can exploit chained authorization flaws in n8n's credential pipeline to steal plaintext secrets from generic HTTP credentials (httpBasicAuth, httpHeaderAuth, httpQueryAuth) belonging to other users. The attack combines a name-based credential resolution path lacking ownership enforcement with a permission checker bypass that skips generic HTTP credential types during pre-execution validation. Community Edition only; Enterprise Edition is protected by additional permission gates.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.123.27>= 2.0.0, < 2.13.3= 2.14.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check n8n versionRun `n8n --version` or check the version via the UI (Settings > About) or API endpoint `/healthz` which returns version infoAffected if The installed version is < 1.123.27, OR >= 2.0.0 and < 2.13.3, OR exactly 2.14.0
-
Confirm Community EditionCheck the UI footer or Settings > About page for 'Community Edition' label, or query the API endpoint `/settings` and look for 'isCached' response indicating community vs enterpriseAffected if Running Community Edition (Enterprise Edition has additional permission gates that protect against this flaw)
-
Identify generic HTTP credentialsNavigate to Credentials section in n8n UI and filter for credentials using httpBasicAuth, httpHeaderAuth, or httpQueryAuth authentication typesAffected if Any generic HTTP credentials (httpBasicAuth, httpHeaderAuth, httpQueryAuth) exist in the system owned by other users
-
Verify user role assignmentCheck user settings or API `/users` endpoint to determine if any non-admin user has the global:member roleAffected if Users with global:member role exist alongside credentials owned by different users
You are affected if running a vulnerable n8n Community Edition version AND have generic HTTP credentials (httpBasicAuth/httpHeaderAuth/httpQueryAuth) created by users other than those with global:member role.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.123.272.13.3
Upgrade to n8n versions 1.123.27, 2.13.3, or 2.14.1 or later. If immediate upgrade is not feasible, restrict instance access to trusted users and audit/rotate any exposed generic HTTP credentials as temporary mitigation.
1.123.27 for 1.x installations; 2.14.1 or 2.13.3 for 2.x installations
- Identify your current n8n installation version and major version line (1.x or 2.x)
- For 1.x users: Upgrade to version 1.123.27 or later
- For 2.x users: If currently on 2.14.0, upgrade to 2.14.1; otherwise upgrade to 2.13.3 or later
- After upgrading, verify the installation succeeded and test that workflows using credentials function correctly
- As a secondary precaution, audit existing generic HTTP credentials (httpBasicAuth, httpHeaderAuth, httpQueryAuth) and consider rotating any that may have been exposed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33663 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33663 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data