Vulnerabilities

Vulnerability · CVE-2026-9749

This issue can occur when running an aggregation pipeline that uses the internal $exchange stage configured with key-range partitioning and order-preserving delivery.

Published Jun 9, 2026 · catalog updated Jul 23, 2026 · This issue can occur

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-9749. EPSS is 0.27%. Act only if a listed version of This issue can occur is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (This issue can occur).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.27%
Remediation
Version ranges on file
Affected products
cpe mongodb/mongodb

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe mongodb/mongodb< 7.0.35
  • cpe mongodb/mongodb< 8.0.24
  • cpe mongodb/mongodb< 8.2.10
  • cpe mongodb/mongodb< 8.3.3

How to fix CVE-2026-9749

  • Upgrade

    CVE-2026-9749 lists a fix boundary at 7.0.35. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 7.0.35

  • Advisory

    Open the inventory_high record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-9749. EPSS is 0.27%. Act only if a listed version of This issue can occur is installed.

Which versions are affected?

Compare what you have installed with < 7.0.35, < 8.0.24, < 8.2.10, < 8.3.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-617. EPSS 0.27%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 9, 2026 · Monitored products — high

    Detected

    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

  2. Jul 23, 2026 · Monitored products — high

    Updated

    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

Sources

  • Monitored products — highVendor advisoryCVE-2026-9749

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 1, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Monitored products — highNov 1, 2026