MongoDBDatabase / datastore
CVE-2025-13644
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 experience an invariant failure during batched delete operations when handling documents. The issue arises when the server mistakenly assumes the presence of multiple documents in a batch based solely on document size exceeding BSONObjMaxSize. This issue affects MongoDB Server v7.0 versions prior to 7.0.26, MongoDB Server v8.0 versions prior to 8.0.13, 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 confidenceMongoDB Server contains an invariant failure vulnerability in its batched delete operation logic. The server incorrectly assumes that when a document's size exceeds BSONObjMaxSize, multiple documents must be present in the batch, leading to an assertion failure during delete operations.
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
>= 7.0.0, < 7.0.26>= 8.0.0, < 8.0.13>= 8.1.0, < 8.1.2= 8.2.0CVSS 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.
-
Check installed MongoDB Server versionRun 'db.version()' in the mongo shell, or execute 'mongod --version' / 'mongos --version' from the command lineAffected if The installed version falls within 7.0.0 to 7.0.25, 8.0.0 to 8.0.12, 8.1.0 to 8.1.1, or equals 8.2.0
-
Identify if batched delete operations are in useReview application code or database logs for bulk delete operations using deleteMany(), delete(), or bulk delete executionAffected if Batched delete operations are being performed against collections containing documents that could approach or exceed BSONObjMaxSize (16MB default)
-
Inspect MongoDB logs for assertion failuresCheck MongoDB server logs (default location /var/log/mongodb/ or /data/log/) for messages containing 'Invariant failure' or 'assertion' related to batched delete or BSONObjMaxSizeAffected if Logs contain assertion failures triggered during delete batch processing
-
Verify document sizes in targeted collectionsRun 'db.collection.find().sort({_id:1}).limit(1).explain()' or check average object size via db.collection.stats() to estimate if large documents existAffected if Collections targeted by delete operations contain documents approaching or exceeding 16MB (BSONObjMaxSize)
You are affected if your MongoDB Server version is within the vulnerable ranges AND you perform batched delete operations on collections with documents that exceed BSONObjMaxSize, or you observe invariant assertion failures in logs during delete operations.
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 · scoped7.0.268.0.138.1.2
Upgrade MongoDB Server to version 7.0.26, 8.0.13, 8.1.2 or later to receive the vendor patch that corrects the batch size assumption logic.
Upgrade to MongoDB Server 7.0.26+, 8.0.13+, 8.1.2+, or latest 8.2.x stable
- 1. Identify the current MongoDB Server version using: db.version() or mongod --version
- 2. For MongoDB 7.0.x users: Plan upgrade to version 7.0.26 or later
- 3. For MongoDB 8.0.x users: Plan upgrade to version 8.0.13 or later
- 4. For MongoDB 8.1.x users: Plan upgrade to version 8.1.2 or later
- 5. For MongoDB 8.2.0 users: Upgrade to the latest 8.2.x stable release (8.2.1 or later if available)
- 6. Before upgrading, ensure proper backup of all databases
- 7. Test the upgrade in a non-production environment first
- 8. During maintenance window, stop MongoDB service, install the new version, and restart
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
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13644 — 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-13644 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