CVE-2026-1850 json
An authorized user may disable the MongoDB server by issuing a certain type of complex query due to boolean expression simplification
published 8mo ago modified 2mo ago also BIT-mongodb-2026-1850 , EUVD-2026-6754
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
Complex queries can cause excessive memory usage in MongoDB Query Planner resulting in an Out-Of-Memory Crash.
Patch / fix
- bitnami mongodb 8.0.18, 8.2.4
- MongoDB Inc MongoDB Server 8.0.18, 8.2.4
Is CVE-2026-1850 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 4.0 | 7.1 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=8.0.0, <8.0.18 >=8.2.0, <8.2.4 |
8.0.18 8.2.4 |
Affected products
- MongoDB Inc MongoDB Server
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-114126
vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-1850
web
Sources
- CVE List CVE-2026-1850
- NVD CVE-2026-1850
- OSV BIT-mongodb-2026-1850
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.