MongoDBDatabase / datastore
CVE-2025-13507
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 · uneditedInconsistent object size validation in time series processing logic may result in later processing of oversized BSON documents leading to an assert failing and process termination. This issue impacts MongoDB Server v7.0 versions prior to 7.0.26, v8.0 versions prior to 8.0.16 and MongoDB server v8.2 versions prior to 8.2.1.
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 confidenceInconsistent object size validation in MongoDB's time series processing logic allows oversized BSON documents to proceed through processing, eventually triggering an assertion failure that terminates the process. This is a denial of service vulnerability affecting time series collections.
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.16>= 8.2.0, < 8.2.1CVSS 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 server versionRun db.version() in the mongo shell or execute 'mongod --version' from command lineAffected if Version is 7.0.0-7.0.25, 8.0.0-8.0.15, or 8.2.0 (all minor versions below 8.2.1)
-
Identify time series collectionsRun db.getCollectionInfos({type: 'timeseries'}) in the mongo shell to list all time series collections in the databaseAffected if Any time series collections exist in the database AND the server version is in the affected range from step 1
-
Verify time series bucket collection settingsInspect one time series collection with db.getCollection('your_timeseries_collection').stats() to confirm bucket configurationAffected if Collection is confirmed as time series type AND server version is in affected range
You are affected if your MongoDB server version falls within 7.0.0-7.0.25, 8.0.0-8.0.15, or 8.2.0 and you have time series collections in use, as oversized BSON documents in those collections can trigger the assertion failure.
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.168.2.1
Upgrade MongoDB Server to version 7.0.26+, 8.0.16+, or 8.2.1+ to patch the size validation inconsistency in time series processing.
MongoDB 7.0.26 / 8.0.16 / 8.2.1 (minimum fixed version based on your branch)
- Determine your current MongoDB version using: db.version()
- Identify which version branch you are on (7.0.x, 8.0.x, or 8.2.x)
- For 7.0.x users: Upgrade to MongoDB Server 7.0.26 or later
- For 8.0.x users (prior to 8.2): Upgrade to MongoDB Server 8.0.16 or later
- For 8.2.x users: Upgrade to MongoDB Server 8.2.1 or later
- Backup your data before upgrading using mongodump
- Stop the MongoDB service gracefully
- Install the new version using your package manager or binary installation method
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation3.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13507 — 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-13507 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