CVE-2026-9749 Affecting mongod-8.2 package, versions <8.2.11-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.47% (39th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-MONGOD82-17388686
  • published20 Jun 2026
  • disclosed9 Jun 2026

Introduced: 9 Jun 2026

CVE-2026-9749  (opens in a new tab)

How to fix?

Upgrade Minimos:latest mongod-8.2 to version 8.2.11-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream mongod-8.2 package and not the mongod-8.2 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.