CVE-2026-9749

published 9 Jun 2026 · updated 10 Jun 2026

Using MaxKey() may crash the server

6.5MediumCVSS 6.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Server 7.0.35, Server 8.0.24, Server 8.2.10 and 1 more.

This issue can occur when running an aggregation pipeline that uses the internal $exchange stage configured with key-range partitioning and order-preserving delivery. If a single key range produces enough documents to fill its exchange buffer (that is, many results are routed to the same consumer), the server reaches the code path where a full per-consumer buffer is detected but the internal "high watermark" for that key range is not updated as intended.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MongoDBServer>=7.0.0 <7.0.35, >=8.0.0 <8.0.24, >=8.2.0 <8.2.10, >=8.3.0 <8.3.37.0.35, 8.0.24, 8.2.10, 8.3.3

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in MongoDB, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-9749 severity on Zeptric[![CVE-2026-9749](https://zeptric.io/badge/cve/CVE-2026-9749.svg)](https://zeptric.io/cve/CVE-2026-9749)