CVE-2026-8053 is a memory-safety vulnerability in MongoDB Server’s time-series collection implementation. An authenticated user with database write privileges can trigger an out-of-bounds memory write in the mongod process due to an inconsistency in the internal field-name-to-index mapping within the time-series bucket catalog. Under certain conditions, corruption of process memory can lead to arbitrary code execution. Affected versions are MongoDB Server 5.0 prior to 5.0.33, 6.0 prior to 6.0.28, 7.0 prior to 7.0.34, 8.0 prior to 8.0.23, 8.2 prior to 8.2.9, and 8.3 prior to 8.3.2.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A MongoDB vulnerability involving undefined behavior with duplicate field names in timeseries data.
A MongoDB server denial-of-service vulnerability referenced in the recent vulnerability history table.
A vulnerability impacting MongoDB Server for which MongoDB has patched Atlas deployments and released patched builds for supported self-hosted versions 5.0 and later.
A vulnerability identified as CVE-2026-8053 is referenced, but no technical details are provided because access to the bug report is restricted.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.