CVE-2026-77070: n8n before 1.123.69 NoSQL Injection via MongoDB Node
n8n before 1.123.69, 2.33.4, and 2.34.1 contains a NoSQL injection vulnerability in the MongoDB node's Find, Delete, and Aggregate operations, which parse the Query parameter as JSON after expression resolution without sanitizing MongoDB operators. An attacker who can influence the resolved query (e.g., via externally-controlled data) can inject operators such as $ne or $where, turning an intended single-document lookup into full-collection disclosure, full-collection deletion, or other operations on the database server.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
n8n (MongoDB node)to a version that resolves this vulnerability.Fixed in 1.123.69 - Upgrade
Upgrade
n8n (MongoDB node)to a version that resolves this vulnerability.Fixed in 2.33.4 - Upgrade
Upgrade
n8n (MongoDB node)to a version that resolves this vulnerability.Fixed in 2.34.1 - Compensating control
If you can’t immediately upgrade, prevent attackers from influencing the MongoDB node’s resolved Query parameter (e.g., ensure externally-controlled data cannot be used to build/resolve the Query JSON that is passed to Find/Delete/Aggregate).
Event History
Frequently Asked Questions
Which workflows are exposed to this issue?
Workflows using the MongoDB node's Find, Delete, or Aggregate operations are exposed when their Query parameter can be influenced by externally controlled data after expression resolution.
What does an attacker need to exploit it?
An attacker needs a way to influence the resolved MongoDB query. This can occur when workflow expressions place externally controlled data into the Query parameter.
What could exploitation allow?
Injected MongoDB operators such as $ne or $where can change an intended single-document lookup into full-collection disclosure, full-collection deletion, or other operations on the database server.
Which versions contain the fixes?
The issue affects versions before 1.123.69, 2.33.4, and 2.34.1. Updating to the applicable listed release or later addresses the affected version range.