dbcve.org
MongoDBDatabase / datastore

CVE-2025-3084

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 5.0.31 / 6.0.20 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
When run on commands with certain arguments set, explain may fail to validate these arguments before using them. This can lead to crashes in router servers. This affects MongoDB Server v5.0 prior to 5.0.31, MongoDB Server v6.0 prior to 6.0.20, MongoDB Server v7.0 prior to 7.0.16 and MongoDB Server v8.0 prior to 8.0.4

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

The MongoDB Server 'explain' feature fails to validate certain command arguments before using them, leading to crashes in router servers (mongos instances). This is a denial-of-service vulnerability affecting specific versions of MongoDB 5.0, 6.0, 7.0, and 8.0.

MitigationUpgrade MongoDB Server to version 5.0.31 or higher, 6.0.20 or higher, 7.0.16 or higher, or 8.0.4 or higher to patch the argument validation 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:>= 5.0.0, < 5.0.31>= 6.0.0, < 6.0.20>= 7.0.0, < 7.0.16>= 8.0.0, < 8.0.4

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 MongoDB Server version
    Run 'db.version()' in the MongoDB shell or execute 'mongod --version' from the command line to obtain the installed MongoDB Server version.
    Affected if The version falls within any of these ranges: 5.0.0 to 5.0.30, 6.0.0 to 6.0.19, 7.0.0 to 7.0.15, or 8.0.0 to 8.0.3.
  2. Confirm mongos router instances are deployed
    Run 'db.adminCommand({getParameter: 1, clusterRole: 1})' or check running processes for 'mongos' to determine if MongoDB router instances are in use.
    Affected if mongos router instances are running. The vulnerability affects crashes in mongos, not standalone mongod instances.
  3. Verify explain command usage
    Review application code and query patterns for usage of the 'explain' method on queries, such as 'db.collection.find({}).explain()' or equivalent driver methods.
    Affected if The explain feature is actively used against the mongos instance. This is the attack vector for triggering the crash.
  4. Check for recent mongos crash logs
    Examine MongoDB log files (typically in /var/log/mongodb/ or the configured log path) for entries containing 'explain' and 'crash' or 'assertion' failures occurring around the time of explain command execution.
    Affected if Crash logs or assertions related to explain commands are present in the mongos logs.

A user is affected if they run any mongos router instance with a version in the affected ranges and actively use the explain feature, which can trigger crashes.

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 5.0.31 / 6.0.20 / 7.0.16 or later
Fixed in 5.0.316.0.207.0.16
Interim mitigation

Upgrade MongoDB Server to version 5.0.31 or higher, 6.0.20 or higher, 7.0.16 or higher, or 8.0.4 or higher to patch the argument validation vulnerability.

Recommended fix High confidence

Upgrade to the minimum fixed version for your current major release line (5.0.31, 6.0.20, 7.0.16, or 8.0.4)

  1. 1. Identify the current MongoDB Server version by running: db.version() in the mongo shell or checking the mongod --version output
  2. 2. Determine which major version line you are running (5.0.x, 6.0.x, 7.0.x, or 8.0.x)
  3. 3. For MongoDB 5.0.x: Upgrade to version 5.0.31 or later
  4. 4. For MongoDB 6.0.x: Upgrade to version 6.0.20 or later
  5. 5. For MongoDB 7.0.x: Upgrade to version 7.0.16 or later
  6. 6. For MongoDB 8.0.x: Upgrade to version 8.0.4 or later
  7. 7. Before upgrading in production, test the new version in a staging environment
  8. 8. Follow standard MongoDB upgrade procedures including backing up data
Caveat Patch upgrades within the same major version typically have minimal breaking changes; however, review MongoDB release notes for any noted changes

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
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

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