VYPR
Medium severity6.5NVD Advisory· Published Jun 9, 2026· Updated Jun 10, 2026

CVE-2026-9749

CVE-2026-9749

Description

MongoDB aggregation pipeline issue with $exchange stage can lead to server instability or denial of service.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

MongoDB aggregation pipeline issue with $exchange stage can lead to server instability or denial of service.

Vulnerability

A bug in MongoDB's aggregation pipeline, specifically within the internal $exchange stage when configured with key-range partitioning and order-preserving delivery, can occur. If a single key range generates a large number of documents that fill its exchange buffer, the server fails to update the internal "high watermark" for that key range, leading to a detected full per-consumer buffer.

Exploitation

An attacker would need to trigger an aggregation pipeline using the $exchange stage with key-range partitioning and order-preserving delivery. The attacker must then provide input that causes a single key range to produce enough documents to fill its exchange buffer, thereby reaching the vulnerable code path.

Impact

When the vulnerable code path is reached, the server may experience instability or a denial of service. The exact impact is not fully detailed in the available references, but it relates to the internal handling of buffer states within the aggregation pipeline.

Mitigation

This issue has been fixed. The reference indicates that the resolution is "Fixed" with no specific version mentioned, but it is associated with a Jira ticket for MongoDB server development [1]. No specific workaround is provided, and the vulnerability is not listed as part of the KEV catalog.

AI Insight generated on Jun 9, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

1