CVE-2026-8843
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 · uneditedCreating a "2dsphere_bucket" index on a non-timeseries bucket collection will succeed, but any subsequent attempt to insert a document which triggers updating that index will crash the server. A similar issue occurs when creating "queryable_encrypted_range" indices. This issue affects MongoDB Server v7.0 versions prior to 7.0.32, v8.0 versions prior to 8.0.21 and v8.2 versions prior to 8.2.6
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 confidenceA denial of service vulnerability in MongoDB Server allows creation of '2dsphere_bucket' or 'queryable_encrypted_range' indexes on non-timeseries bucket collections. When documents are subsequently inserted that would update these indexes, the server crashes. This occurs due to incorrect index type validation during document insertion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 'mongod --version' from command lineAffected if Version is earlier than 7.0.32, earlier than 8.0.21, or between 8.0.0 and 8.2.5 (not including 8.2.6+)
-
Identify 2dsphere_bucket indexesRun db.getCollectionNames().forEach(function(c) { db.getCollection(c).getIndexes().forEach(function(i) { if (i.key && i.key.v && i.key._id && i.name.includes('2dsphere_bucket')) print(c + ': ' + i.name); }); });Affected if Any collection returns a 2dsphere_bucket index name in the output
-
Identify queryable_encrypted_range indexesRun db.getCollectionNames().forEach(function(c) { db.getCollection(c).getIndexes().forEach(function(i) { if (i.key && i.name && i.name.includes('queryable_encrypted_range')) print(c + ': ' + i.name); }); });Affected if Any collection returns a queryable_encrypted_range index name in the output
-
Verify if affected indexes are on timeseries bucket collectionsFor each collection identified in steps 2-3, run db.getCollection('<collectionName>').stats() and check if 'timeseries' field exists in the output or check the original timeseries collection using db.getCollection('<timeseriesName>').stats().bucketCountAffected if The index exists on a collection that is NOT a timeseries bucket collection (the collection lacks timeseries properties)
You are affected if your MongoDB version is before the patched versions AND you have 2dsphere_bucket or queryable_encrypted_range indexes created on non-timeseries collections.
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 · scopedUpgrade to MongoDB Server v7.0.32+, v8.0.21+, or v8.2.6+ to patch the vulnerability. Additionally, audit existing deployments for any incorrectly created indexes on non-timeseries collections and recreate them after patching.
7.0.32 / 8.0.21 / 8.2.6 (depending on your current branch)
- Identify your current MongoDB Server version using db.version() or mongod --version
- If running v7.0.x, upgrade to v7.0.32 or later
- If running v8.0.x, upgrade to v8.0.21 or later
- If running v8.2.x, upgrade to v8.2.6 or later
- After upgrading, verify the server starts successfully and test index operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8843 — 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-8843 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