Home

Description

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.

PUBLISHED Reserved 2026-05-27 | Published 2026-06-09 | Updated 2026-06-10 | Assigner mongodb




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

MEDIUM: 6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Problem types

CWE-617 Reachable assertion

Product status

Default status
unaffected

8.3.0 (semver) before 8.3.3
affected

8.2.0 (semver) before 8.2.10
affected

8.0.0 (semver) before 8.0.24
affected

7.0.0 (semver) before 7.0.35
affected

References

jira.mongodb.org/browse/SERVER-124031

cve.org (CVE-2026-9749)

nvd.nist.gov (CVE-2026-9749)

Download JSON