CVE-2025-3084 json
MongoDB Server may crash due to improper validation of explain command
published last yr. modified 2mo ago also BIT-mongodb-2025-3084 , EUVD-2025-9312
- 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 35%
- public exploits
- 0
- none known
Summary
When run on commands with certain arguments set, explain may fail to validate these arguments before using them. This can lead to crashes in router servers. This affects MongoDB Server v5.0 prior to 5.0.31, MongoDB Server v6.0 prior to 6.0.20, MongoDB Server v7.0 prior to 7.0.16 and MongoDB Server v8.0 prior to 8.0.4
Patch / fix
- bitnami mongodb 5.0.31, 6.0.20, 7.0.16, 8.0.4
- MongoDB Inc MongoDB Server 5.0.31, 6.0.20, 7.0.16, 8.0.4
Is CVE-2025-3084 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
- last yr.
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=5.0.0, <5.0.31 >=6.0.0, <6.0.20 >=7.0.0, <7.0.16 >=8.0.0, <8.0.4 |
5.0.31 6.0.20 7.0.16 8.0.4 |
Affected products
- MongoDB Inc MongoDB Server
Classification
- Weakness
-
- CWE-703 Improper Check or Handling of Exceptional Conditions
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-103153
issue-tracking, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-3084
web
Sources
- CVE List CVE-2025-3084
- NVD CVE-2025-3084
- OSV BIT-mongodb-2025-3084
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.