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.
{
"severity": "High",
"cpes": [
"cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:*"
]
}