CVE-2026-6914 json
MD5 checksum creation may cause availability loss
published 2026-04-29 6 mo ago modified 2026-10-26 13 d ago also BIT-mongodb-2026-6914 , EUVD-2026-26262
- 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 17%
- public exploits
- 0
- none known
Summary
Computing the MD5 checksum of a malformed BSON object under specific conditions may cause loss of availability in MongoDB server. This issue affects all MongoDB Server v8.2 versions, all MongoDB Server v8.1 versions, MongoDB Server v8.0 versions prior to 8.0.21, MongoDB Server v7.0 versions prior to 7.0.32
Patch / fix
- bitnami mongodb 7.0.32, 8.0.21, 8.2.7
- MongoDB MongoDB Server 7.0.32, 8.0.21, 8.2.7
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% 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 |
| 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 | >=7.0.0, <7.0.32 >=8.0.0, <8.0.21 >=8.1.0, <8.2.7 |
7.0.32 8.0.21 8.2.7 |
Affected products
- MongoDB MongoDB Server
Classification
- Weakness
-
- CWE-191 Integer Underflow (Wrap or Wraparound)
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-119981
issue-tracking, patch
-
nvd.nist.gov
/vuln/detail/CVE-2026-6914
web
Sources
- CVE List CVE-2026-6914
- NVD CVE-2026-6914
- OSV BIT-mongodb-2026-6914
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.