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.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
>= 7.0.0, < 7.0.35CPE matchmatch criteria | cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:* | ||
>= 8.0.0, < 8.0.24CPE matchmatch criteria | cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:* | ||
>= 8.2.0, < 8.2.10CPE matchmatch criteria | cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:* | ||
>= 8.3.0, < 8.3.3CPE matchmatch criteria | cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:* |
CVSS version used by this source: 4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.1 Bluesky, 0.0 Mastodon, and 0.1 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.0 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.