CVE-2026-33665

Workarounds

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

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 application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2026-33665 has a CVSS score of 8.2 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.4.0, 1.121.0); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-33665? CVE-2026-33665 is a high-severity improper authentication vulnerability in n8n (npm), affecting versions >= 2.0.0-rc.0, < 2.4.0. It is fixed in 2.4.0, 1.121.0. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2026-33665? CVE-2026-33665 has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of n8n are affected by CVE-2026-33665? n8n (npm) versions >= 2.0.0-rc.0, < 2.4.0 is affected.
4. Is there a fix for CVE-2026-33665? Yes. CVE-2026-33665 is fixed in 2.4.0, 1.121.0. Upgrade to this version or later.
5. Is CVE-2026-33665 exploitable, and should I be worried? Whether CVE-2026-33665 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33665 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33665?
   • Upgrade n8n to 2.4.0 or later
   • Upgrade n8n to 1.121.0 or later