NVD / CVE Program· CNA GitHub_M

CVE-2026-33663: n8n Vulnerable to Credential Theft via Name-Based Resolution and Permission Checker Bypass in Community Edition

Noroxi assessment

Priority: Monitor (action score 34/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: n8n (npm) 2.13.3, 2.14.1, 1.123.27.

Low priority for now. Upgrade to n8n (npm) 2.13.3, 2.14.1, 1.123.27 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

n8n 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.

HighCVSS 8.5 · v4.0—No exploit Fix available

Broken access control (IDOR)

GHSA-m63j-689w-3j35

Published: Mar 25, 2026
Updated: Jun 17, 2026
EPSS: 0.3% · 34th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 34 / 40 · 8.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 8.5; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
n8n	n8n	cpe:2.3:a:n8n:n8n

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

n8n n8nbefore 1.123.27
n8n n8n2.0.0 and later · before 2.13.3
n8n n8n2.14.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

n8n-io n8n
- < 1.123.27, >= 2.0.0-rc.0, < 2.13.3, = 2.14.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
npm	n8n	from 2.0.0-rc.0 · before 2.13.3	2.13.3
npm	n8n	from 2.14.0 · before 2.14.1	2.14.1
npm	n8n	before 1.123.27	1.123.27

Same product

n8n: all records

Other highest-scoring records for the same primary product.

CVE-2025-68613n8n Vulnerable to Remote Code Execution via Expression InjectionKEV
95Now
CVE-2026-21858n8n Vulnerable to Unauthenticated File Access via Improper Webhook Request Handling
63This week
CVE-2026-1470Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.
45Plan

Published before and after this one in the same product

← EarlierCVE-2026-27496Mar 25, 2026 · n8n has In-Process Memory Disclosure in its Task Runner
28Monitor
← EarlierCVE-2026-33660Mar 25, 2026 · n8n Has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL Mode
37Monitor
Later →CVE-2026-33665Mar 25, 2026 · n8n: LDAP Email-Based Account Linking Allows Privilege Escalation and Account Takeover
35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
npm:n8n	1.123.27	Package registry (OSV)
npm:n8n	2.13.3	Package registry (OSV)
npm:n8n	2.14.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-4573290 days apartn8n: Cross-user Authorization Bypass in Dynamic Credential OAuth Endpoints
33Monitor
CVE-2026-65016119 days apartn8n before 1.123.64, 2.29.8, and 2.30.1 Privilege Escalation via SSO Instance-Role
30Monitor
CVE-2026-77079148 days apartn8n before 2.34.1 Authorization Bypass via Custom Role Deletion
29Monitor
CVE-2026-72763139 days apartn8n before 1.123.67 Credential Exfiltration via Sub-Workflow
28Monitor
CVE-2026-72774139 days apartn8n before 1.123.67 Authentication Bypass via HTTP Request Node
28Monitor
CVE-2026-337240 days apartn8n's Source Control SSH Configuration Uses StrictHostKeyChecking=no
25Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/n8n-io/n8n/security/advisories/GHSA-m63j-689w-3j35

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records