CVSS 4.0
5.3 mediumCVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:HCVE-2026-126383 n8n before 1.123.89 NoSQL Injection via MongoDB Node Update Key
Medium (5.3) in n8n-io n8n. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
n8n before 1.123.89, 2.x before 2.45.5, 2.46.x before 2.46.1, and 3.x before 3.0.1 contains a NoSQL injection vulnerability in the MongoDB node's Update and Find And Replace operations due to insufficient validation of the update key value taken from incoming items. Attackers who can supply untrusted input, such as a webhook body, to a workflow using these operations can make the node match and overwrite unintended documents or insert new documents in the MongoDB database.
Severity
CVSS 3.1
8.2 highCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-943 Improper Neutralization of Special Elements in Data Query Logic
- Published
- Modified
- Assigned by
- VulnCheck (CNA)
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126383 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126383?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126383?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126383 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126383)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126383"><img src="https://cve.bz/cve/badge/CVE-2026-126383.svg" alt="CVE-2026-126383"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| n8n-io n8n | before 1.123.89 |
| n8n-io n8n | from 2.46.0 before 2.46.1 |
| n8n-io n8n | from 2.0.0 before 2.45.5 |
| n8n-io n8n | from 3.0.0 before 3.0.1 |
Attack patterns (CAPEC)
- CAPEC-676 NoSQL Injection Likelihood: High · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.
History
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.