Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticated LDAP user modifies email attribute
-
DeliveryLDAP email matches administrator account
-
Exploitn8n auto-links LDAP identity to admin account
-
ExecutionAttacker logs in as administrator
-
ImpactGains full account access and persistence
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK
2 techniques across 2 tactics: Defense Evasion, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires n8n versions before 2.4.0 or 1.121.0 with LDAP authentication enabled. Attacker must be an authenticated LDAP user who can control their own LDAP email attribute, setting it to match a target user's email (including administrators) to hijack their account upon next login. |
| Impact | The real-world risk is moderate to high for organizations using LDAP authentication with n8n, but limited in overall scope. The CVSS 4.0 score of 8.8 reflects network-based attack vector (AV:N), low complexity (AC:L), and high confidentiality and integrity impact (VC:H, VI:H), but requires low privileges (PR:L) and presents attack complexity prerequisites (AT:P) since LDAP must be configured and the attacker needs control over their LDAP email attribute. The vulnerability requires non-default LDAP configuration, significantly reducing the attack surface compared to default installations. Without EPSS data or KEV status indicating active exploitation, and given the requirement for authenticated LDAP access and directory write permissions, this represents a serious but targeted risk primarily for organizations using LDAP with permissive directory configurations. The persistence of the account takeover after email reversion elevates the severity for affected deployments. |
| Exploit ScenarioDerived | An authenticated LDAP user with permission to modify their own directory email attribute changes it to match an administrator's email address (e.g., admin@company.com). Upon their next login to n8n, the platform automatically links their LDAP identity to the administrator account, granting them full administrative access. The attacker then reverts their LDAP email to its original value, but retains permanent access to the compromised administrator account through the persistent linkage. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 25, 2026
Authenticated n8n users can hijack administrator accounts when LDAP authentication is enabled by manipulating their LDAP email attribute to match a target account's email address, gaining full access that persists even after reverting the email change. This authentication bypass (CWE-287) affects n8n versions prior to 2.4.0 and 1.121.0 where LDAP is configured, and public exploit code exists. The vulnerability requires LDAP to be actively enabled and the attacker to control their own LDAP email attribute, creating a critical account takeover risk for administrators.
Earlier versions of this analysis (1)
An authentication bypass vulnerability exists in n8n workflow automation platform when LDAP authentication is configured (non-default). Attackers with valid LDAP credentials who can modify their own LDAP email attribute can set it to match any user's email (including administrators), triggering automatic account linkage and gaining permanent access to the victim's account, even after reverting the LDAP email change. No evidence of active exploitation (not in CISA KEV) is currently available, though the vulnerability has a high CVSS score of 8.8.
RemediationAI
Upgrade n8n to version 2.4.0 or 1.121.0 or later to fully remediate this vulnerability, as detailed in the GitHub security advisory at https://github.com/n8n-io/n8n/security/advisories/GHSA-c545-x2rh-82fc. If immediate patching is not feasible, implement temporary mitigations including disabling LDAP authentication entirely until upgrade is possible, restricting LDAP directory permissions to prevent users from modifying their own email attributes, and conducting a comprehensive audit of existing LDAP-linked accounts to identify and remediate any unexpected or unauthorized account associations. Note that these workarounds provide only partial risk reduction and should be considered short-term measures only.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in npm, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability affects n8n (CPE: cpe:2.3:a:n8n-io:n8n), an open-source workflow automation platform written in TypeScript. The root cause is classified as CWE-287 (Improper Authentication), specifically an insecure automatic account linking mechanism in the LDAP authentication module. When LDAP authentication is enabled, n8n performs email-based matching to link LDAP identities with existing local accounts without proper validation or authorization checks. This trust boundary violation allows authenticated LDAP users to manipulate their directory email attribute to impersonate other users, bypassing intended authentication controls and establishing persistent unauthorized account associations.
Know when N8n gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
3DescriptionGitHub Advisory
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.
Executive ViewAI
A critical authentication bypass vulnerability in n8n allows attackers with valid LDAP credentials to hijack administrator and user accounts by modifying their email attributes, gaining permanent unauthorized access. Organizations using LDAP authentication face immediate risk of account takeover and privilege escalation, with no vendor patch currently available to remediate the threat.
Disable LDAP email auto-linking feature and require manual account linkage verification; restrict LDAP email attribute modification permissions to directory administrators only; implement network segmentation to limit LDAP/n8n connectivity to trusted administrative networks; enforce multi-factor authentication on all n8n administrator accounts independent of LDAP; deploy Web Application Firewall (WAF) rules to log and alert on suspicious account linkage attempts; conduct daily audit logs review for unauthorized account linkage activities; consider disabling LDAP authentication entirely until patch is available if workflow automation can temporarily use alternative authentication.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Related Vulnerabilities in n8n Workflow Automation Multiple Flaws
View all 3Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation
n8n workflow automation (through 1.121.2) allows authenticated users to execute arbitrary code via the n8n service, with
n8n workflow automation (1.65.0 to 1.121.0) allows unauthenticated file access through form-based workflows. A critical
n8n has a fifth critical RCE vulnerability (CVSS 9.9) in the Expression evaluator, enabling code execution through craft
Authenticated users who can create or modify an n8n workflow can achieve remote code execution on the n8n host by abusin
A prototype pollution vulnerability in the XML and GSuiteAdmin nodes of n8n workflow automation platform allows authenti
An authenticated user with workflow creation or modification privileges in n8n workflow automation platform can exploit
n8n-workflows Main Commit ee25413 allows attackers to execute a directory traversal via the download_workflow function w
The n8n package 0.218.0 for Node.js allows Escalation of Privileges. Rated high severity (CVSS 8.8), this vulnerability
Authenticated users can exploit string formatting and exception handling in n8n's Python task executor to escape sandbox
n8n workflow automation platform Community Edition contains an authorization bypass vulnerability allowing authenticated
EUVD-2026-15944
GHSA-c545-x2rh-82fc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB