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.
Remediation
References
Related Vulnerabilities
GlassFish Improper Authentication Vulnerability (CVE-2017-1000030)
Oracle Application Server CVE-2006-5364 Vulnerability (CVE-2006-5364)
WordPress Plugin user files Arbitrary File Upload (2.4.2)
Perl Out-of-bounds Write Vulnerability (CVE-2018-6913)
Kong Server Incorrect Authorization Vulnerability (CVE-2021-27306)