MongoDBDatabase / datastore
CVE-2026-25613
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 · uneditedAn authorized user may disable the MongoDB server by issuing a query against a collection that contains an invalid compound wildcard index.
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 · moderate confidenceThis is a denial-of-service vulnerability in MongoDB where an authenticated user can crash the server by querying a collection that contains an invalid compound wildcard index. The vulnerability is triggered when the server processes a query against a specially crafted or malformed wildcard index definition.
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.29>= 8.0.0, < 8.0.18>= 8.2.0, < 8.2.4CVSS 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.adminCommand({buildInfo: 1})` or `db.version()` to retrieve the installed versionAffected if Version is >= 7.0.0 and < 7.0.29, OR >= 8.0.0 and < 8.0.18, OR >= 8.2.0 and < 8.2.4
-
Identify collections with wildcard indexesQuery `db.system.indexes.find({key: {$exists: true}})` or iterate collections with `db.getCollectionNames().forEach(c => printjson(db[c].getIndexes()))` to list all index definitionsAffected if Any collection contains a wildcard index definition (index with key containing `$**`)
-
Detect compound wildcard indexesExamine the index keys from the previous step: look for wildcard indexes that include additional fields alongside `$**` (e.g., `{"fieldA": 1, "$**": 1}`)Affected if A compound wildcard index exists that combines `$**` with one or more other fields
-
Inspect wildcard index definitions for invalid patternsReview the full index definition using `db.collection.getIndexes()` and check for malformed or corrupted index specifications, particularly in the key patternAffected if The compound wildcard index definition contains syntax errors, missing required parameters, or other structural issues that make it invalid or malformed
A user is affected if their MongoDB version is in the vulnerable range AND they have an invalid compound wildcard index defined on any collection that can be queried by an authenticated user.
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.298.0.188.2.4
Apply the official MongoDB patch/upgrade when available. Until then, restrict database access to trusted authenticated users and audit existing collections for invalid compound wildcard index definitions.
7.0.29 (or latest 7.0.x), 8.0.18 (or latest 8.0.x), 8.2.4 (or latest 8.2.x)
- 1. Schedule a maintenance window and back up all MongoDB data
- 2. For MongoDB 7.0.x: upgrade to version 7.0.29 or later
- 3. For MongoDB 8.0.x: upgrade to version 8.0.18 or later
- 4. For MongoDB 8.2.x: upgrade to version 8.2.4 or later
- 5. Restart the MongoDB server with the new version
- 6. Verify the server starts successfully and accepts connections
- 7. Test that queries against collections with compound wildcard indexes work correctly
- 8. Validate application functionality against the upgraded database
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MongoDB
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25613 — 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-2026-25613 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