CVE-2026-33751

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

• Limit workflow creation and editing permissions to fully trusted users only.
• Disable the LDAP node by adding n8n-nodes-base.ldap to the NODES_EXCLUDE environment variable.
• Avoid passing unvalidated external user input into LDAP node search parameters via expressions.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

A flaw in the LDAP node's filter escape logic allowed LDAP metacharacters to pass through unescaped when user-controlled input was interpolated into LDAP search filters. In workflows where external user input is passed via expressions into the LDAP node's search parameters, an attacker could manipulate the constructed filter to retrieve unintended LDAP records or bypass authentication checks implemented in the workflow.

Exploitation requires a specific workflow configuration:

• The LDAP node must be used with user-controlled input passed via expressions (e.g., from a form or webhook).

CVE-2026-33751 has a CVSS score of 4.8 (Medium). The vector is network-reachable, no 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 (1.123.27, 2.14.1, 2.13.3); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2026-33751? CVE-2026-33751 is a medium-severity security vulnerability in n8n (npm), affecting versions < 1.123.27. It is fixed in 1.123.27, 2.14.1, 2.13.3.
2. How severe is CVE-2026-33751? CVE-2026-33751 has a CVSS score of 4.8 (Medium). 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-33751? n8n (npm) versions < 1.123.27 is affected.
4. Is there a fix for CVE-2026-33751? Yes. CVE-2026-33751 is fixed in 1.123.27, 2.14.1, 2.13.3. Upgrade to this version or later.
5. Is CVE-2026-33751 exploitable, and should I be worried? Whether CVE-2026-33751 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-33751 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-33751?
   • Upgrade n8n to 1.123.27 or later
   • Upgrade n8n to 2.14.1 or later
   • Upgrade n8n to 2.13.3 or later