dbcve.org
MongoDBDatabase / datastore

CVE-2026-8199

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 7.0.34 / 8.0.23 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An authenticated user can cause excess memory usage via bitwise match expression AST processing of $bitsAllSet, $bitsAnySet, $bitsAllClear, and $bitsAnyClear. This contributes to memory pressure and may lead to availability loss by OOM. This issue impacts MongoDB Server v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.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 confidence

This is a memory exhaustion vulnerability in MongoDB where authenticated users can exploit bitwise match operators ($bitsAllSet, $bitsAnySet, $bitsAllClear, $bitsAnyClear) to cause excess memory consumption during AST processing. The unbounded memory usage leads to OOM conditions and availability loss.

MitigationUpgrade MongoDB Server to v7.0.34+, v8.0.23+, v8.2.9+, or v8.3.2+ to patch the memory exhaustion vulnerability in bitwise expression AST processing.

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
Affected:>= 7.0.0, < 7.0.34>= 8.0.0, < 8.0.23>= 8.2.0, < 8.2.9>= 8.3.0, < 8.3.2

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MongoDB server version
    Run 'db.version()' in mongosh or 'mongod --version' from command line to obtain the installed MongoDB version
    Affected if Version is >= 7.0.0 and < 7.0.34, OR >= 8.0.0 and < 8.0.23, OR >= 8.2.0 and < 8.2.9, OR >= 8.3.0 and < 8.3.2
  2. Locate queries using bitwise match operators
    Search application code, mongod logs, or profiler output for queries containing $bitsAllSet, $bitsAnySet, $bitsAllClear, or $bitsAnyClear operators
    Affected if Bitwise match operators are actively used in any query against the database
  3. Verify if authentication is enabled
    Check mongod configuration (--auth flag or security.authorization setting in config file) or run 'db.adminCommand({getParameter: 1, authSchemaVersion: 1})' in mongosh
    Affected if Authentication is disabled (unauthenticated users could not trigger this specific vulnerability, though this is not a mitigating factor for overall security)

Environment is affected if MongoDB version falls within the affected ranges AND bitwise match operators are being used in queries against the database

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.0.34 / 8.0.23 / 8.2.9 or later
Fixed in 7.0.348.0.238.2.9
Interim mitigation

Upgrade MongoDB Server to v7.0.34+, v8.0.23+, v8.2.9+, or v8.3.2+ to patch the memory exhaustion vulnerability in bitwise expression AST processing.

Recommended fix High confidence

7.0.34, 8.0.23, 8.2.9, or 8.3.2 (depending on current major version branch)

  1. 1. Check current MongoDB Server version using: db.version() or mongod --version
  2. 2. Based on current version, identify target fixed release: if 7.0.x upgrade to 7.0.34, if 8.0.x upgrade to 8.0.23, if 8.2.x upgrade to 8.2.9, if 8.3.x upgrade to 8.3.2
  3. 3. Review MongoDB upgrade documentation for your current major version for prerequisites and compatibility checks
  4. 4. Create a full backup of all databases before upgrading
  5. 5. Stop the MongoDB instance
  6. 6. Upgrade MongoDB Server packages to the appropriate fixed version using your package manager (e.g., apt, yum, or tarball)
  7. 7. Verify the new version installed: mongod --version
  8. 8. Start MongoDB and verify all replica set members or sharded cluster nodes are operational
Caveat Review MongoDB release notes between your current version and target version for any backward-incompatible changes or feature removals

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MongoDB Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8199 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8199 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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