dbcve.org
MongoDBDatabase / datastore

CVE-2026-8053

HIGH · 8.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 5.0.33 / 6.0.28 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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 issue in MongoDB Server's time-series collection implementation allows an authenticated user with database write privileges to trigger an out-of-bounds memory write in the mongod process. The issue results from an inconsistency in the internal field-name-to-index mapping within the time-series bucket catalog. Under certain conditions this can result in arbitrary code execution. This issue impacts MongoDB Server v5.0 versions prior to 5.0.33, v6.0 versions prior to 6.0.28, 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
How this class of weakness works · CWE-787

The program writes past the bounds of a buffer, overwriting adjacent memory an attacker can turn to their advantage. Crafted input can overwrite control data and redirect execution. Remediation is validating every index and length before a write, plus modern memory-safety mitigations.

General guidance for the out-of-bounds write class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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:>= 5.0.0, < 5.0.33>= 6.0.0, < 6.0.28>= 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 5.0.33 / 6.0.28 / 7.0.34 or later
Fixed in 5.0.336.0.287.0.34
Vendor patch jira.mongodb.org →
Recommended fix High confidence

Minimum fixed versions: 5.0.33, 6.0.28, 7.0.34, or 8.0.23 (choose based on your current major version branch)

  1. 1. Identify the currently installed MongoDB version by running: db.version() in the mongo shell or mongosh
  2. 2. Determine which version branch your current installation belongs to (5.0, 6.0, 7.0, or 8.0)
  3. 3. For MongoDB 5.0.x: upgrade to version 5.0.33 or later
  4. 4. For MongoDB 6.0.x: upgrade to version 6.0.28 or later
  5. 5. For MongoDB 7.0.x: upgrade to version 7.0.34 or later
  6. 6. For MongoDB 8.0.x: upgrade to version 8.0.23 or later
  7. 7. Follow the official MongoDB upgrade guide for your version path: https://www.mongodb.com/docs/manual/release-notes/
  8. 8. Before upgrading production systems, test the upgrade in a staging environment
Caveat MongoDB upgrades between major versions may require careful migration planning; review breaking changes in release notes for your version path before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8053 — 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-8053 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