MongoDB Server router will crash when incorrect lsid is set on a sharded query

published 2025-09-05 14 mo ago modified 2026-09-08 2 mo 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 21%
public exploits: 0; none known

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

fixed in 2

bitnami mongodb 6.0.24, 7.0.18, 8.0.6
MongoDB Inc MongoDB Server 6.0.24, 7.0.18, 8.0.6

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 14 mo ago (2025-09-05)

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).

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

MongoDB rss critical rss

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

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.

Summary