n8n: N8n before 1.123.69, 2.33.4, and 2.34.1 contains a NoSQL injection vulnerability in the MongoDB…
n8n
- Severity
- Critical, CVSS 9.8
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Record
- CVE-2026-77070
- Affects
- n8n
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- August 20, 2026
- Source last modified
- September 1, 2026
Description
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.
Description quoted from the NVD record.
Who is affected
n8n is a tool for automating work by linking apps and services into step-by-step workflows. This flaw affects n8n versions before 1.123.69, 2.33.4 and 2.34.1. The problem is in the building block that connects a workflow to a MongoDB database when it is used to find, delete or summarize records. If an attacker can influence the search that block runs, for example through data that comes from an outside source, they could turn a lookup meant for one record into one that reveals or deletes a whole set of stored records. They could also carry out other actions on the database server. This flaw is rated Critical.
What to do
- The person who installed or runs n8n for your organization should handle this. If an IT provider or vendor runs it for you, send them this advisory and ask when the update will be done.
- Check which version of n8n you are running and whether any of your workflows use the MongoDB building block.
- Update n8n to version
1.123.69,2.33.4or2.34.1or later, choosing the one that fits the version you run now. - For details on the fix, see the vendor advisory linked on this page.
Analysis written from the source record as of September 1, 2026 and reviewed before publishing.