CVE-2025-10059 json
MongoDB Server router will crash when incorrect lsid is set on a sharded query
published last yr. modified 2mo ago also BIT-mongodb-2025-10059 , EUVD-2025-27046
- 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 22%
- public exploits
- 0
- none known
Summary
An improper setting of the lsid field on any sharded query can cause a crash in MongoDB routers. This issue occurs when a generic argument (lsid) is provided in a case when it is not applicable. This affects MongoDB Server v6.0 versions prior to 6.0.x, MongoDB Server v7.0 versions prior to 7.0.18 and MongoDB Server v8.0 versions prior to 8.0.6.
Patch / fix
- bitnami mongodb 6.0.24, 7.0.18, 8.0.6
- MongoDB Inc MongoDB Server 6.0.24, 7.0.18, 8.0.6
Is CVE-2025-10059 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.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-11).
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 | >=6.0.0, <6.0.24 >=7.0.0, <7.0.18 >=8.0.0, <8.0.6 |
6.0.24 7.0.18 8.0.6 |
Affected products
- MongoDB Inc MongoDB Server
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-100901
issue-tracking, vendor-advisory, advisory
-
jira.mongodb.org
/browse/SERVER-100909
issue-tracking, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-10059
web
Sources
- CVE List CVE-2025-10059
- NVD CVE-2025-10059
- OSV BIT-mongodb-2025-10059
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.