dbcve.org
MongoDBDatabase / datastore

CVE-2026-25610

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 7.0.29 / 8.0.13 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An authorized user may trigger a server crash by running a $geoNear pipeline with certain invalid index hints.

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 · moderate confidence

This is a denial-of-service vulnerability in MongoDB where an authenticated user can trigger a server crash by executing a $geoNear aggregation pipeline with certain invalid index hints. The vulnerability stems from improper handling or validation of index hints passed to the $geoNear stage, causing the server to crash when processing malformed input.

MitigationApply the vendor patch from MongoDB when available. In the interim, restrict database access to trusted authenticated users and monitor for unusual $geoNear pipeline executions that may indicate exploitation attempts.

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
Affected:>= 7.0.0, < 7.0.29>= 8.0.0, < 8.0.13

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MongoDB version
    Run db.version() in the mongo shell or use mongod --version from command line
    Affected if Version is >= 7.0.0 and < 7.0.29, or >= 8.0.0 and < 8.0.13
  2. Locate $geoNear aggregation executions in logs
    Search MongoDB log files (default path /var/log/mongodb/) or query the system.log collection for entries containing '$geoNear' and 'indexHint' or similar warnings
    Affected if Logs show $geoNear pipeline executions with index hints that produced errors or warnings
  3. Review server crash logs for $geoNear context
    Examine MongoDB diagnostic files in the dbPath (typically /data/db/) or system logs for crashdump files timestamped around unexpected shutdowns
    Affected if Crash logs or core dumps reference the $geoNear stage or index hint processing code
  4. Check audit logs for authenticated $geoNear operations
    If auditing is enabled, query the audit collection or log files for aggregation pipeline executions containing $geoNear with the 'hint' option
    Affected if Audit logs show $geoNear aggregations with index hints executed by any authenticated user

A user is affected if their MongoDB version falls within the vulnerable ranges AND there is evidence of $geoNear aggregation with index hints triggering server crashes or errors in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.0.29 / 8.0.13 or later
Fixed in 7.0.298.0.13
Interim mitigation

Apply the vendor patch from MongoDB when available. In the interim, restrict database access to trusted authenticated users and monitor for unusual $geoNear pipeline executions that may indicate exploitation attempts.

Recommended fix High confidence

MongoDB 7.0.29+ or 8.0.13+

  1. Backup your MongoDB database before upgrading
  2. For MongoDB Community Server: Download and install version 7.0.29 or higher (for 7.x) or 8.0.13 or higher (for 8.x) from the official MongoDB download center at https://www.mongodb.com/try/download/community
  3. For MongoDB Atlas: Upgrade your cluster to MongoDB 7.0.29+ or 8.0.13+ through the Atlas UI or Atlas Administration API
  4. After upgrading, verify that the $geoNear pipeline operations function correctly with valid index hints
  5. Confirm that the server no longer crashes when using $geoNear with invalid index hints
Caveat Review MongoDB release notes for breaking changes between your current version and the target fixed version

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25610 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25610 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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