Skip to content
Noroxi
CVE-2026-18693· NVD / CVE Program· CNA mongodb

Out-of-Bounds Read/Write in MongoDB Timeseries Bucket Handling Leads to Denial of Service and Potential Memory Disclosure

An issue in MongoDB Server's handling of timeseries collections could allow an authenticated user with write privileges to cause an internal data structure to become inconsistent through certain document insertions. A subsequent insert into the affected bucket could then result in the server accessing memory outside its intended bounds, potentially causing a server crash (denial of service), exposure of limited memory contents, or memory corruption.

HighCVSS 7.2 · v4.0—No exploit Fix available
Published
Aug 11, 2026
Updated
Sep 16, 2026
EPSS
0.3% · 25th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.2 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · mongodb
7.2
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
mongodbmongodb

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • mongodb mongodb7.0.0 and later · before 7.0.40
  • mongodb mongodb8.0.0 and later · before 8.0.29
  • mongodb mongodb8.2.0 and later · up to 8.2.12 inclusive
  • mongodb mongodb8.3.0 and later · before 8.3.8
  • mongodb mongodb9.0.0
  • mongodb mongodb9.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mongodb). Independent of NVD's CPE analysis and usually ahead of it.

  • MongoDB MongoDB Server

    • 8.3.0 and later · before 8.3.8affected · semver
    • 8.0 and later · before 8.0.29affected · semver
    • 7.0 and later · before 7.0.40affected · semver

Other highest-scoring records for the same primary product.

  • CVE-2025-14847Zlib compressed protocol header length confusion may allow memory readKEV
    89Now
  • CVE-2025-3085MongoDB Server running on Linux may allow unexpected connections where intermediate certificates are revoked
    39Monitor
  • CVE-2024-8654MongoDB Server may access non-initialized region of memory leading to unexpected behaviour
    39Monitor
  • CVE-2024-1351MongoDB Server may allow successful untrusted connection
    39Monitor
  • CVE-2013-1892MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMonkey, which allows r
    37Monitor
  • CVE-2026-82067Improper Case Sensitivity Handling in MongoDB Server Configuration Validation May Cause Authorization to Remain Disabled at Startup
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
MongoDB MongoDB Server7.0.40Vendor (CNA)
MongoDB MongoDB Server8.0.29Vendor (CNA)
MongoDB MongoDB Server8.3.8Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-1193361 days apartPost-authentication use-after-free in server-side JavaScript BSON-to-array conversion
    34Monitor
  • CVE-2026-805390 days apartFlatBSON Duplicate Field Index Drift
    34Monitor
  • CVE-2026-8207128 days apartInsufficient Validation of Storage Engine Configuration Options in MongoDB Server Leads to Out-of-Bounds Write
    28Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records