CVE-2026-54313
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedn8n is an open source workflow automation platform. Prior to 2.24.0, an authenticated user with workflow edit access could supply a malicious filter value in the MongoDB node's Find And Replace operation. The value was not validated before being passed to MongoDB as a query filter, allowing unintended documents to be matched and overwritten with attacker-controlled content. This vulnerability is fixed in 2.24.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn n8n versions prior to 2.24.0, the MongoDB node's Find And Replace operation lacks proper input validation on filter values. An authenticated user with workflow edit access can supply a malicious filter that bypasses the intended query scope, allowing matching and overwriting of unintended MongoDB documents with attacker-controlled content.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.24.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check n8n versionRun 'npx n8n --version' or check the package.json file in your n8n installation directory for the 'version' fieldAffected if The version listed is less than 2.24.0
-
Identify MongoDB nodes in workflowsQuery your n8n database for workflows containing nodes with type 'n8n-nodes-base.mongoDb' or inspect workflow JSON exports for 'mongoDb' node entriesAffected if Workflows contain MongoDB nodes and the n8n version is below 2.24.0
-
Verify MongoDB node uses Find And Replace operationExamine the MongoDB node configuration in affected workflows and check if the 'operation' parameter is set to 'findAndReplace'Affected if A MongoDB node is configured with the Find And Replace operation and the n8n version is below 2.24.0
-
Review workflow access permissionsCheck which users have edit access to workflows containing vulnerable MongoDB nodes via the n8n UI under Workflow Settings or by querying the workflow permissions in the databaseAffected if Multiple users or non-admin users have edit access to workflows with MongoDB Find And Replace nodes
You are affected if your n8n installation version is below 2.24.0 and workflows exist that use the MongoDB node with the Find And Replace operation accessible to users with workflow edit permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.24.0
Upgrade n8n to version 2.24.0 or later to obtain the patched code that validates filter values before executing MongoDB queries.
2.24.0
- 1. Back up your n8n instance and database before upgrading
- 2. Upgrade n8n to version 2.24.0 or later
- 3. Verify the upgrade was successful by checking the n8n version in the UI or via CLI
- 4. Test the MongoDB node workflows to ensure normal operation after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54313 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54313 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data