MongoDBDatabase / datastore
CVE-2025-6712
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 · uneditedMongoDB Server may be susceptible to disruption caused by high memory usage, potentially leading to server crash. This condition is linked to inefficiencies in memory management related to internal operations. In scenarios where certain internal processes persist longer than anticipated, memory consumption can increase, potentially impacting server stability and availability. This issue affects MongoDB Server v8.0 versions prior to 8.0.10
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 confidenceMongoDB Server v8.0 contains a memory management inefficiency where certain internal processes persist longer than anticipated, causing excessive memory consumption that can lead to server crash and impact availability.
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
>= 8.0.0, < 8.0.10CVSS 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.
-
Check MongoDB version via shellConnect to the MongoDB instance using mongosh or mongo shell and run: db.version()Affected if The returned version is >= 8.0.0 and < 8.0.10 (e.g., 8.0.0, 8.0.5, 8.0.9)
-
Check mongod binary versionRun the command: mongod --versionAffected if The version displayed is between 8.0.0 and 8.0.9 inclusive
-
Check installed package versionOn Linux systems, run: dpkg -l | grep mongodb-server (Debian/Ubuntu) or rpm -qa | grep mongodb (RHEL/CentOS)Affected if The package version shows an 8.0.x version where x is less than 10
-
Check MongoDB service statusRun: systemctl status mongod or ps aux | grep mongod to confirm the service is runningAffected if The running service is based on an affected 8.0.0-8.0.9 version
You are affected if your MongoDB Server installation version is 8.0.0 through 8.0.9 inclusive; versions 8.0.10 and later, or versions before 8.0.0, are not vulnerable to this memory management inefficiency.
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 · scoped8.0.10
Upgrade MongoDB Server to version 8.0.10 or later to resolve the memory management inefficiency.
MongoDB 8.0.10
- Back up your MongoDB data before starting the upgrade process
- Review the MongoDB upgrade documentation for version 8.0.10
- Stop the MongoDB server gracefully
- Upgrade MongoDB Server to version 8.0.10 or later
- Start the MongoDB server and verify it runs successfully
- Monitor server memory usage to confirm the issue is resolved
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
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6712 — 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-6712 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