CVE-2025-3083 json
Malformed MongoDB wire protocol messages may cause mongos to crash
published last yr. modified 2mo ago also BIT-mongodb-2025-3083 , EUVD-2025-9313
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
Specifically crafted MongoDB wire protocol messages can cause mongos to crash during command validation. This can occur without using an authenticated connection. This issue affects MongoDB v5.0 versions prior to 5.0.31, MongoDB v6.0 versions prior to 6.0.20 and MongoDB v7.0 versions prior to 7.0.16
Patch / fix
- bitnami mongodb 5.0.31, 6.0.20, 7.0.16
- MongoDB Inc MongoDB Server 5.0.31, 6.0.20, 7.0.16
Is CVE-2025-3083 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
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 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 | >=5.0.0, <5.0.31 >=6.0.0, <6.0.20 >=7.0.0, <7.0.16 |
5.0.31 6.0.20 7.0.16 |
Affected products
- MongoDB Inc MongoDB Server
Classification
- Weakness
-
- CWE-248 Uncaught Exception
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-103152
issue-tracking, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-3083
web
Sources
- CVE List CVE-2025-3083
- NVD CVE-2025-3083
- OSV BIT-mongodb-2025-3083
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.