CVE-2026-18700 json
Use-After-Free in MongoDB Geospatial Validation Leads to Denial of Service
published 2026-08-11 2 mo ago modified 2026-10-23 16 d ago also BIT-mongodb-2026-18700 , EUVD-2026-56913
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
An issue in MongoDB Server's geospatial validation could allow an authenticated user with write privileges to cause an internal reference to be used after the underlying memory has been freed, through concurrent operations against a collection using a certain type of validator. This could result in a server crash, leading to a denial of service.
Patch / fix
- bitnami mongodb 7.0.40, 8.0.29, 8.3.8, 9.0.2
- MongoDB MongoDB Server 7.0.40, 8.0.29, 8.3.8
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:L/AT:P/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 | 6.0 | CVSS:4.0/AV:N/AC:L/AT:P/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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=7.0.0, <7.0.40 >=8.0.0, <8.0.29 >=8.2.0, <8.3.8 >=9.0.0, <9.0.2 |
7.0.40 8.0.29 8.3.8 9.0.2 |
Affected products
- MongoDB MongoDB Server
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-130117
vendor-advisory, issue-tracking, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-18700
web
Sources
- CVE List CVE-2026-18700
- NVD CVE-2026-18700
- OSV BIT-mongodb-2026-18700
Fencer Vulns 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.