NVD / CVE Program· CNA GitHub_M

CVE-2026-33665: n8n: LDAP Email-Based Account Linking Allows Privilege Escalation and Account Takeover

Noroxi assessment

Priority: Monitor (action score 35/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.33% (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.4.0, 1.121.0.

Low priority for now. Upgrade to n8n (npm) 2.4.0, 1.121.0 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.4.0 and 1.121.0, when LDAP authentication is enabled, n8n automatically linked an LDAP identity to an existing local account if the LDAP email attribute matched the local account's email. An authenticated LDAP user who could control their own LDAP email attribute could set it to match another user's email — including an administrator's — and upon login gain full access to that account. The account linkage persisted even if the LDAP email was later reverted, resulting in a permanent account takeover. LDAP authentication must be configured and active (non-default). The issue has been fixed in n8n versions 2.4.0 and 1.121.0. 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: Disable LDAP authentication until the instance can be upgraded, restrict LDAP directory permissions so that users cannot modify their own email attributes, and/or audit existing LDAP-linked accounts for unexpected account associations. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

HighCVSS 8.8 · v4.0—No exploit Fix available

Auth bypass

GHSA-c545-x2rh-82fc

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

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

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

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

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.121.0
n8n n8n2.0.0 and later · before 2.4.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.121.0, >= 2.0.0-rc.0, < 2.4.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.4.0	2.4.0
npm	n8n	before 1.121.0	1.121.0

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-33660Mar 25, 2026 · n8n Has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL Mode
37Monitor
← EarlierCVE-2026-33663Mar 25, 2026 · n8n Vulnerable to Credential Theft via Name-Based Resolution and Permission Checker Bypass in Community Edition
34Monitor
Later →CVE-2026-33696Mar 25, 2026 · n8n Vulnerable to Prototype Pollution in XML & GSuiteAdmin node parameters lead to RCE
37Monitor

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.121.0	Package registry (OSV)
npm:n8n	2.4.0	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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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-59208106 days apartn8n: Cross-Issuer Token Exchange Account Binding via Subject-Only Identity Resolution
30Monitor
CVE-2026-56353112 days apartn8n - Authentication Bypass in Chat Trigger Node
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.

CVE-2026-336600 days apartn8n Has Multiple Remote Code Execution Vulnerabilities in Merge Node AlaSQL SQL Mode
37Monitor
CVE-2026-336960 days apartn8n Vulnerable to Prototype Pollution in XML & GSuiteAdmin node parameters lead to RCE
37Monitor
CVE-2026-2749828 days apartn8n has Arbitrary Command Execution via File Write and Git Operations
36Monitor
CVE-2026-337130 days apartn8n Vulnerable to SQL Injection in Data Table Node via orderByColumn Expression
34Monitor

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-287 · Improper Authentication

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:L/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

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

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

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

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

Attack patterns (CAPEC)

ATT&CK techniques

Change log

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

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

References

github.com/n8n-io/n8n/security/advisories/GHSA-c545-x2rh-82fc

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

All records