CVE-2025-10059: MongoDB Server · Incorrect Permissions
Affects MongoDB ServerSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDB Inc MongoDB Server | Affected
| Fixed in– |
AI-suggested
1. Immediate patching: Organizations should prioritize upgrading MongoDB Server to versions 6.0.x or later, 7.0.18 or later, and 8.0.6 or later as soon as patches become available. 2. Access control: Restrict privileges to only trusted users and applications that can issue sharded queries, minimizing the risk of unauthorized or malformed lsid parameters. 3. Query validation: Implement application-layer validation to ensure that lsid parameters are only sent when applicable, preventing malformed queries from reaching the database. 4. Monitoring and alerting: Deploy monitoring on MongoDB router logs and metrics to detect abnormal crashes or restarts indicative of exploitation attempts. 5. Network segmentation: Isolate MongoDB routers within secure network segments to reduce exposure to untrusted networks and limit attack surface. 6. Incident response readiness: Prepare response plans for potential denial of service incidents affecting database availability, including failover and backup strategies. 7. Vendor communication: Maintain close contact with MongoDB Inc for updates, patches, and advisories related to this vulnerability.
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.