MongoDBDatabase / datastore
CVE-2025-3083
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 · uneditedSpecifically crafted MongoDB wire protocol messages can cause mongos to crash during command validation. This can occur without using an authenticated connection. This issue affects MongoDB v5.0 versions prior to 5.0.31, MongoDB v6.0 versions prior to 6.0.20 and MongoDB v7.0 versions prior to 7.0.16
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 confidenceSpecifically crafted MongoDB wire protocol messages cause mongos (the sharding router) to crash during command validation without requiring authentication, resulting in 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
>= 5.0.0, < 5.0.31>= 6.0.0, < 6.0.20>= 7.0.0, < 7.0.16CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 is runningRun 'ps aux | grep mongos' or check for mongos process in your process listAffected if mongos process is present and running
-
Determine MongoDB versionRun 'db.version()' if connected to mongos, or 'mongos --version' from the command lineAffected if version is 5.0.0 to 5.0.30, 6.0.0 to 6.0.19, or 7.0.0 to 7.0.15
-
Verify mongos network exposureCheck mongos configuration file for 'net.bind_ip' settings or review firewall rules controlling access to port 27017Affected if mongos is bound to a network interface accessible from untrusted networks (0.0.0.0 or public IP)
Environment is affected if mongos is running a version between 5.0.0-5.0.30, 6.0.0-6.0.19, or 7.0.0-7.0.15 and is network accessible to untrusted parties.
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 · scoped5.0.316.0.207.0.16
Upgrade MongoDB to version 5.0.31 or higher for v5.0, 6.0.20 or higher for v6.0, or 7.0.16 or higher for v7.0.
MongoDB 5.0.31 / 6.0.20 / 7.0.16 (depending on your major version branch)
- 1. Determine your current MongoDB version by running: db.version() in the mongo shell or mongosh
- 2. Identify whether you are running mongos (sharding router), mongod (shard server), or both
- 3. For MongoDB 5.0.x: Plan upgrade to version 5.0.31 or later
- 4. For MongoDB 6.0.x: Plan upgrade to version 6.0.20 or later
- 5. For MongoDB 7.0.x: Plan upgrade to version 7.0.16 or later
- 6. Review MongoDB upgrade documentation for your specific version path (https://www.mongodb.com/docs/manual/release-notes/)
- 7. Back up your data before performing the upgrade
- 8. Perform the upgrade following standard MongoDB upgrade procedures
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3083 — 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-3083 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