n8n-io n8n up to 1.123.88/2.45.4/2.46.0/3.0.0 MongoDB node update key sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00+ |
Summary
A vulnerability, which was classified as critical, was found in n8n-io n8n up to 1.123.88/2.45.4/2.46.0/3.0.0. Affected by this vulnerability is an unknown functionality of the component MongoDB node. The manipulation of the argument update key results in sql injection. This vulnerability was named CVE-2026-126383. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in n8n-io n8n up to 1.123.88/2.45.4/2.46.0/3.0.0. Affected is some unknown functionality of the component MongoDB node. The manipulation of the argument update key with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-126383 since 11/10/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
Upgrading to version 1.123.89, 2.45.5, 2.46.1 or 3.0.1 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 1.123.0
- 1.123.1
- 1.123.2
- 1.123.3
- 1.123.4
- 1.123.5
- 1.123.6
- 1.123.7
- 1.123.8
- 1.123.9
- 1.123.10
- 1.123.11
- 1.123.12
- 1.123.13
- 1.123.14
- 1.123.15
- 1.123.16
- 1.123.17
- 1.123.18
- 1.123.19
- 1.123.20
- 1.123.21
- 1.123.22
- 1.123.23
- 1.123.24
- 1.123.25
- 1.123.26
- 1.123.27
- 1.123.28
- 1.123.29
- 1.123.30
- 1.123.31
- 1.123.32
- 1.123.33
- 1.123.34
- 1.123.35
- 1.123.36
- 1.123.37
- 1.123.38
- 1.123.39
- 1.123.40
- 1.123.41
- 1.123.42
- 1.123.43
- 1.123.44
- 1.123.45
- 1.123.46
- 1.123.47
- 1.123.48
- 1.123.49
- 1.123.50
- 1.123.51
- 1.123.52
- 1.123.53
- 1.123.54
- 1.123.55
- 1.123.56
- 1.123.57
- 1.123.58
- 1.123.59
- 1.123.60
- 1.123.61
- 1.123.62
- 1.123.63
- 1.123.64
- 1.123.65
- 1.123.66
- 1.123.67
- 1.123.68
- 1.123.69
- 1.123.70
- 1.123.71
- 1.123.72
- 1.123.73
- 1.123.74
- 1.123.75
- 1.123.76
- 1.123.77
- 1.123.78
- 1.123.79
- 1.123.80
- 1.123.81
- 1.123.82
- 1.123.83
- 1.123.84
- 1.123.85
- 1.123.86
- 1.123.87
- 1.123.88
- 2.0
- 2.1
- 2.2
- 2.3
- 2.4
- 2.5
- 2.6
- 2.7
- 2.8
- 2.9
- 2.10
- 2.11
- 2.12
- 2.13
- 2.14
- 2.15
- 2.16
- 2.17
- 2.18
- 2.19
- 2.20
- 2.21
- 2.22
- 2.23
- 2.24
- 2.25
- 2.26
- 2.27
- 2.28
- 2.29
- 2.30
- 2.31
- 2.32
- 2.33
- 2.34
- 2.35
- 2.36
- 2.37
- 2.38
- 2.39
- 2.40
- 2.41
- 2.42
- 2.43
- 2.44
- 2.45
- 2.45.0
- 2.45.1
- 2.45.2
- 2.45.3
- 2.45.4
- 2.46.0
- 3.0
Website
- Product: https://github.com/n8n-io/n8n/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 7.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: n8n 1.123.89/2.45.5/2.46.1/3.0.1
Timeline
11/10/2026 CVE reserved11/13/2026 Advisory disclosed
11/13/2026 VulDB entry created
11/13/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: VulnCheck
CVE: CVE-2026-126383 (🔒)
GCVE (CVE): GCVE-0-2026-126383
GCVE (VulDB): GCVE-100-436788
Entry
Created: 11/13/2026 11:27Changes: 11/13/2026 11:27 (77)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.