n8n: NoSQL Injection in MongoDB Node Find And Replace Operation
- Product
- n8n
- CVE
- CVE-2026-54313
- Affected
- n8n < 2.24.0
- Fixed in
- 2.24.0
Last verified against sources: October 26, 2026
Am I affected?
n8n: affected n8n < 2.24.0. Fixed in 2.24.0.
- Check your version: run
npm ls n8n. Versions < 2.24.0 of n8n are affected. [1]
What to do now
- Upgrade to the fixed version: run
npm install n8n@2.24.0(first patched version 2.24.0). [1] - Upgrade to n8n version 2.24.0 or later. [1]
- Limit workflow creation and editing permissions to fully trusted users only. [1]
- Disable the MongoDB node by adding
n8n-nodes-base.mongoDbto theNODES_EXCLUDEenvironment variable. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
Impact
- Unintended documents could be matched and overwritten with attacker-controlled content. [1]
What was done
Sources
- GHSA-jpq7-226w-6cxx — GitHub Advisory Database
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
[CVE-2026-54313] n8n: NoSQL Injection in MongoDB Node Find And Replace Operation
Product: n8n | Affected: n8n < 2.24.0 | Fixed in: 2.24.0
Summary: An authenticated user with workflow edit access could supply a malicious filter value in the MongoDB node's Find And Replace operation.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/06/cve-2026-54313-n8nCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for CVE-2026-54313
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.