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.
{
"cna_assigner": "mongodb",
"cwe_ids": [
"CWE-617"
],
"unresolved_ranges": [
{
"source": "AFFECTED_FIELD",
"extracted_events": [
{
"introduced": "8.3.0"
},
{
"fixed": "8.3.3"
},
{
"introduced": "8.2.0"
},
{
"fixed": "8.2.10"
},
{
"introduced": "8.0.0"
},
{
"fixed": "8.0.24"
},
{
"introduced": "7.0.0"
},
{
"fixed": "7.0.35"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/9xxx/CVE-2026-9749.json"
}{
"source": "CPE_RANGE",
"cpe": "cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:*",
"extracted_events": [
{
"introduced": "7.0.0"
},
{
"fixed": "7.0.35"
},
{
"introduced": "8.0.0"
},
{
"fixed": "8.0.24"
},
{
"introduced": "8.2.0"
},
{
"fixed": "8.2.10"
},
{
"introduced": "8.3.0"
},
{
"fixed": "8.3.3"
}
]
}