CVE-2026-33751: n8n · LDAP Injection
Affects n8nSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.13.3 or 1.123.27 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.13.3, 1.123.27
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade n8n to 2.13.3 or 1.123.27; n8n-io/n8n to 1.123.27.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n8n-ion8n | Affected
| Fixed in
|
npmn8n-io/n8npkg:npm/n8n-io/n8nOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.