MongoDBDatabase / datastore
CVE-2025-10059
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImproper handling of the lsid (logical session ID) field in sharded queries causes MongoDB routers (mongos) to crash. When lsid is provided in contexts where it's not applicable, the router fails to process the query correctly, leading to denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MongoDBDatabase / datastore
>= 6.0.0, < 6.0.24>= 7.0.0, < 7.0.18>= 8.0.0, < 8.0.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if mongos processes are runningRun 'ps aux | grep mongos' or check your MongoDB cluster topology to confirm if mongos router processes are deployed. This vulnerability affects the mongos router, not standalone mongod instances.Affected if mongos processes are running in your environment
-
Check MongoDB server versionRun 'db.version()' connected through mongos, or run 'mongos --version' on each mongos host, or check via 'db.adminCommand({buildInfo:1})' to retrieve the exact version number.Affected if The version is 6.0.0 to 6.0.23, 7.0.0 to 7.0.17, or 8.0.0 to 8.0.5
-
Confirm sharded cluster configurationRun 'sh.status()' or check your configuration for shard clusters. This issue specifically affects sharded queries through mongos.Affected if A sharded cluster deployment is in use with one or more shards configured
-
Review query patterns for lsid usageExamine application query logs or profiler output for queries that include the 'lsid' field. This vulnerability triggers when lsid is provided in contexts where it's not applicable to sharded operations.Affected if Applications are sending lsid (logical session ID) in sharded queries to mongos
You are affected if you run a vulnerable MongoDB version (6.0.0-6.0.23, 7.0.0-7.0.17, or 8.0.0-8.0.5) with mongos in a sharded cluster configuration, and your queries include lsid in contexts where it should not be used.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.0.247.0.188.0.6
Upgrade MongoDB Server to version 6.0.x, 7.0.18, or 8.0.6 or later to patch the vulnerability. Test the upgrade in a staging environment before production deployment.
6.0.24 (for 6.0.x) | 7.0.18 (for 7.0.x) | 8.0.6 (for 8.0.x)
- Identify the current MongoDB version using: db.version() or mongod --version
- Determine the appropriate upgrade path based on your current major version (6.0.x, 7.0.x, or 8.0.x)
- For MongoDB 6.0.x: upgrade to version 6.0.24 or later
- For MongoDB 7.0.x: upgrade to version 7.0.18 or later
- For MongoDB 8.0.x: upgrade to version 8.0.6 or later
- Before upgrading in production, test the upgrade in a staging environment
- Ensure proper backups are in place before performing the upgrade
- Follow MongoDB's standard upgrade procedure for your deployment type (standalone, replica set, or sharded cluster)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-10059 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data