You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: MongoDB Server de MongoDB, Description: Este problema puede ocurrir al ejecutar una pipeline de agregación que utiliza la etapa interna $exchange configurada con particionamiento por rango de claves y entrega que preserva el orden. Si un único rango de claves produce suficientes documentos para llenar su búfer de intercambio (es decir, muchos resultados se enrutan al mismo consumidor), el servidor alcanza la ruta de código donde se detecta un búfer completo por consumidor, pero la 'marca de agua alta' interna para ese rango de claves no se actualiza según lo previsto.
Initial Analysis by NIST6/18/2026 10:39:50 AM
Action
Type
Old Value
New Value
Added
CPE Configuration
OR
*cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:* versions from (including) 8.0.0 up to (excluding) 8.0.24
*cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:* versions from (including) 8.2.0 up to (excluding) 8.2.10
*cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:* versions from (including) 8.3.0 up to (excluding) 8.3.3
*cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:* versions from (including) 7.0.0 up to (excluding) 7.0.35
New CVE Received from MongoDB, Inc.6/09/2026 7:17:04 PM
Action
Type
Old Value
New Value
Added
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.