Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-8053: An issue in MongoDB Server's time-series collection implementation allows an authenticated user with database

44
This month
HIGH 8.8UPGRADE

CVE-2026-8053 is a high-severity flaw (CVSS 8.8) affecting mongodb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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,

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.7% (top 49%)
CISA exploited listNo
WeaknessCWE-787
Published2026-05-13
Last modified2026-10-26
Publisher (CNA): MongoDB, Inc. · Vendor: mongodb

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

mongodb mongodb UPGRADE
Affected: >= 5.0.0 and < 5.0.33 · >= 6.0.0 and < 6.0.28 · >= 7.0.0 and < 7.0.34 · >= 8.0.0 and < 8.0.23 · >= 8.2.0 and < 8.2.9 · >= 8.3.0 and < 8.3.2
Fixed in: 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2
Safe to downgrade to: a release before 5.0.0
1. Check installed version
apt-cache policy mongodb || rpm -q mongodb || mongodb --version
2. UPGRADE to 5.0.33 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade mongodb
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade mongodb
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 5.0.0 (Debian / Ubuntu)
apt-cache madison mongodb sudo apt install mongodb=<VERSION_BEFORE_5.0.0> sudo apt-mark hold mongodb
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mongodb sudo dnf downgrade mongodb-<VERSION_BEFORE_5.0.0> sudo dnf versionlock add mongodb
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-8053?

mongodb: upgrade to 5.0.33, 6.0.28, 7.0.34, 8.0.23, 8.2.9, 8.3.2. Exact commands for each OS are on this page.

Is CVE-2026-8053 being exploited?

CVE-2026-8053 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-8053 affect?

CVE-2026-8053 affects mongodb. Severity is high (CVSS 8.8). 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 in

How urgent is CVE-2026-8053?

Priority 44/100. High severity

Software pages

MongoDB vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.