dbcve.org
MongoDBDatabase / datastore

CVE-2025-10061

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-05
Fix available
A fix is available. Upgrade to 6.0.25 / 7.0.22 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 can cause a crash in the MongoDB Server through a specially crafted $group query. This vulnerability is related to the incorrect handling of certain accumulator functions when additional parameters are specified within the $group operation. This vulnerability could lead to denial of service if triggered repeatedly. This issue affects MongoDB Server v6.0 versions prior to 6.0.25, MongoDB Server v7.0 versions prior to 7.0.22, MongoDB Server v8.0 versions prior to 8.0.12 and MongoDB Server v8.1 versions prior to 8.1.2

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 confidence

An authorized user can crash the MongoDB Server via a specially crafted $group query that improperly handles certain accumulator functions when additional parameters are specified. The vulnerability stems from incorrect handling within the aggregation pipeline's $group operation, leading to a denial-of-service condition through repeatable crashes.

MitigationUpgrade MongoDB Server to version 6.0.25 or later, 7.0.22 or later, 8.0.12 or later, or 8.1.2 or later to patch this vulnerability.

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:>= 6.0.0, < 6.0.25>= 7.0.0, < 7.0.22>= 8.0.0, < 8.0.12>= 8.1.0, < 8.1.2

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. Check installed MongoDB version
    Run db.version() in the mongo shell or mongosh, or run mongod --version from the command line
    Affected if The version falls within >= 6.0.0 and < 6.0.25, >= 7.0.0 and < 7.0.22, >= 8.0.0 and < 8.0.12, or >= 8.1.0 and < 8.1.2
  2. Identify $group aggregation usage
    Search application code and database query logs for aggregation pipelines containing the $group stage
    Affected if The database uses $group stages in aggregation pipelines with accumulator functions
  3. Review $group accumulator function usage
    Examine any $group pipelines for use of accumulator functions such as $stdDevPop, $stdDevSamp, $push, $addToSet, or other accumulators that accept additional parameters beyond the field expression
    Affected if The $group stage uses accumulator functions with extra parameters specified (for example, passing options or additional arguments to the accumulator)
  4. Check for server crashes in logs
    Inspect MongoDB server logs (default location /var/log/mongodb/ or the configured log path) for crash reports, stack traces, or abort signals occurring during aggregation pipeline execution
    Affected if Logs show repeatable crashes or assertions related to $group operation processing

You are affected if your MongoDB version is within the vulnerable ranges AND your environment executes $group aggregation pipelines that use accumulator functions with additional parameters.

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 6.0.25 / 7.0.22 / 8.0.12 or later
Fixed in 6.0.257.0.228.0.12
Interim mitigation

Upgrade MongoDB Server to version 6.0.25 or later, 7.0.22 or later, 8.0.12 or later, or 8.1.2 or later to patch this vulnerability.

Recommended fix High confidence

6.0.25 (or 7.0.22 / 8.0.12 / 8.1.2 depending on your current branch)

  1. 1. Review MongoDB release notes for the target version to understand any compatibility considerations
  2. 2. Create a full backup of your MongoDB data before upgrading
  3. 3. Stop the MongoDB server instance
  4. 4. Upgrade MongoDB Server to version 6.0.25 or higher (for 6.0.x branch), 7.0.22 or higher (for 7.0.x branch), 8.0.12 or higher (for 8.0.x branch), or 8.1.2 or higher (for 8.1.x branch)
  5. 5. Verify the upgrade was successful by checking the server version (db.version())
  6. 6. Restart the MongoDB service
  7. 7. Test that $group queries with accumulator functions work correctly
  8. 8. Monitor system stability to confirm the vulnerability is no longer reproducible
Caveat Review MongoDB release notes for your target version; minor version upgrades typically maintain backward compatibility but always verify

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MongoDB Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10061 — 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-2025-10061 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