CVE-2026-33751: CWE-90: Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') in n8n-io n8n
n8n is an open source workflow automation platform. Prior to versions 1.123.27, 2.13.3, and 2.14.1, 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). 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: 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, and/or 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.
AI Analysis
Technical Summary
CVE-2026-33751 is a medium-severity LDAP Injection vulnerability identified in the open-source workflow automation platform n8n. The issue stems from improper neutralization of special LDAP metacharacters within the LDAP node's filter escape logic prior to versions 1.123.27, 2.13.3, and 2.14.1. Specifically, when user-controlled input is interpolated into LDAP search filters via expressions in workflows, the input is not properly escaped, allowing attackers to inject malicious LDAP queries. This can lead to unauthorized retrieval of LDAP records or bypass of authentication mechanisms implemented within the workflow. Exploitation requires a workflow that uses the LDAP node with external user input passed through expressions, such as from forms or webhooks, making the attack vector dependent on specific workflow configurations. The vulnerability does not require authentication or user interaction, increasing its risk if such workflows are exposed. The issue was publicly disclosed and fixed in the specified versions, with no known exploits in the wild at the time of publication. Temporary mitigations include restricting workflow creation and editing to trusted users, disabling the LDAP node via environment variables, and avoiding passing unvalidated external input into LDAP filters. However, these mitigations do not fully eliminate the risk and upgrading remains the recommended solution.
Potential Impact
The impact of this vulnerability is significant for organizations using n8n workflows that integrate with LDAP directories and accept external user input. An attacker exploiting this flaw could manipulate LDAP queries to retrieve sensitive directory information beyond intended scope, potentially exposing user credentials, group memberships, or other confidential data. Additionally, attackers might bypass authentication checks implemented in workflows, leading to unauthorized access to internal systems or data. This could facilitate further lateral movement, privilege escalation, or data exfiltration within affected environments. Since n8n is used globally for automation and integration tasks, organizations relying on LDAP-based authentication or directory lookups in workflows are at risk. The vulnerability's exploitation does not require authentication or user interaction, increasing the threat surface if workflows are exposed to external inputs. However, the need for specific workflow configurations limits the scope somewhat. Overall, the vulnerability poses a medium risk but could have severe consequences in sensitive or high-value environments.
Mitigation Recommendations
To mitigate CVE-2026-33751, organizations should prioritize upgrading n8n to versions 1.123.27, 2.13.3, 2.14.1, or later where the vulnerability is fixed. Until upgrades can be applied, restrict workflow creation and editing permissions strictly to fully trusted administrators to prevent introduction of vulnerable workflows. Consider disabling the LDAP node entirely by adding `n8n-nodes-base.ldap` to the `NODES_EXCLUDE` environment variable to eliminate the attack vector temporarily. Avoid passing any unvalidated or user-controlled external input into LDAP node search parameters via expressions; implement strict input validation and sanitization if such input is necessary. Review existing workflows for use of the LDAP node with external inputs and refactor or remove risky configurations. Monitor logs for unusual LDAP query patterns or unexpected access to directory data. Employ network segmentation and access controls to limit exposure of n8n instances and LDAP servers. Finally, maintain an incident response plan to quickly address any suspected exploitation attempts.
Affected Countries
United States, Germany, United Kingdom, France, Canada, Australia, Netherlands, Japan, India, Brazil
CVE-2026-33751: CWE-90: Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') in n8n-io n8n
Description
n8n is an open source workflow automation platform. Prior to versions 1.123.27, 2.13.3, and 2.14.1, 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). 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: 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, and/or 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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-33751 is a medium-severity LDAP Injection vulnerability identified in the open-source workflow automation platform n8n. The issue stems from improper neutralization of special LDAP metacharacters within the LDAP node's filter escape logic prior to versions 1.123.27, 2.13.3, and 2.14.1. Specifically, when user-controlled input is interpolated into LDAP search filters via expressions in workflows, the input is not properly escaped, allowing attackers to inject malicious LDAP queries. This can lead to unauthorized retrieval of LDAP records or bypass of authentication mechanisms implemented within the workflow. Exploitation requires a workflow that uses the LDAP node with external user input passed through expressions, such as from forms or webhooks, making the attack vector dependent on specific workflow configurations. The vulnerability does not require authentication or user interaction, increasing its risk if such workflows are exposed. The issue was publicly disclosed and fixed in the specified versions, with no known exploits in the wild at the time of publication. Temporary mitigations include restricting workflow creation and editing to trusted users, disabling the LDAP node via environment variables, and avoiding passing unvalidated external input into LDAP filters. However, these mitigations do not fully eliminate the risk and upgrading remains the recommended solution.
Potential Impact
The impact of this vulnerability is significant for organizations using n8n workflows that integrate with LDAP directories and accept external user input. An attacker exploiting this flaw could manipulate LDAP queries to retrieve sensitive directory information beyond intended scope, potentially exposing user credentials, group memberships, or other confidential data. Additionally, attackers might bypass authentication checks implemented in workflows, leading to unauthorized access to internal systems or data. This could facilitate further lateral movement, privilege escalation, or data exfiltration within affected environments. Since n8n is used globally for automation and integration tasks, organizations relying on LDAP-based authentication or directory lookups in workflows are at risk. The vulnerability's exploitation does not require authentication or user interaction, increasing the threat surface if workflows are exposed to external inputs. However, the need for specific workflow configurations limits the scope somewhat. Overall, the vulnerability poses a medium risk but could have severe consequences in sensitive or high-value environments.
Mitigation Recommendations
To mitigate CVE-2026-33751, organizations should prioritize upgrading n8n to versions 1.123.27, 2.13.3, 2.14.1, or later where the vulnerability is fixed. Until upgrades can be applied, restrict workflow creation and editing permissions strictly to fully trusted administrators to prevent introduction of vulnerable workflows. Consider disabling the LDAP node entirely by adding `n8n-nodes-base.ldap` to the `NODES_EXCLUDE` environment variable to eliminate the attack vector temporarily. Avoid passing any unvalidated or user-controlled external input into LDAP node search parameters via expressions; implement strict input validation and sanitization if such input is necessary. Review existing workflows for use of the LDAP node with external inputs and refactor or remove risky configurations. Monitor logs for unusual LDAP query patterns or unexpected access to directory data. Employ network segmentation and access controls to limit exposure of n8n instances and LDAP servers. Finally, maintain an incident response plan to quickly address any suspected exploitation attempts.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-23T18:30:14.125Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69c430e5f4197a8e3b78e0bb
Added to database: 3/25/2026, 7:00:53 PM
Last enriched: 3/25/2026, 7:16:01 PM
Last updated: 3/26/2026, 5:41:12 AM
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.