CVE-2026-8843 json
Calling createIndex with certain index types can crash mongod
published 2026-05-18 5 mo ago modified 2026-10-26 14 d ago also BIT-mongodb-2026-8843 , EUVD-2026-30777
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
Creating a "2dsphere_bucket" index on a non-timeseries bucket collection will succeed, but any subsequent attempt to insert a document which triggers updating that index will crash the server. A similar issue occurs when creating "queryable_encrypted_range" indices.
This issue affects MongoDB Server v7.0 versions prior to 7.0.32, v8.0 versions prior to 8.0.21 and v8.2 versions prior to 8.2.6
Patch / fix
- bitnami mongodb 7.0.32, 8.0.21, 8.2.6
- MongoDB, Inc. MongoDB Server 7.0.32, 8.0.21, 8.2.6
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=7.0.0, <7.0.32 >=8.0.0, <8.0.21 >=8.2.0, <8.2.6 |
7.0.32 8.0.21 8.2.6 |
Affected products
- MongoDB, Inc. MongoDB Server
Classification
- Weakness
-
- CWE-617 Reachable Assertion
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-116327
issue-tracking, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-8843
web
Sources
- CVE List CVE-2026-8843
- NVD CVE-2026-8843
- OSV BIT-mongodb-2026-8843
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.