Skip to main content
Menu
CVEs

MongoDB denial of service in aggregation sub-pipelines

Affects MongoDB Server 9.0.0 up to 9.0.7 builds that include SERVER-119491, which changed expression cloning. Fixed in 9.0.7.

CVE-2026-120821Published November 10, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 9.0.7
Who is exposed
Specific setups only

Summary

A use-after-free flaw in the aggregation framework of MongoDB Server can be triggered remotely by an attacker who has a low-privilege login with read access, and it can cause the server to terminate unexpectedly. The bug is reached when certain expressions are evaluated in an aggregation sub-pipeline, and no user action is needed.

Written by a model

Original description

A use-after-free in the aggregation framework of MongoDB Server can occur when certain expressions are evaluated in an aggregation sub-pipeline. The condition can be caused by an authenticated user with read privileges, and may result in the server terminating unexpectedly.

Who should check

Teams running MongoDB Server 9.0 releases before 9.0.7 that run aggregation pipelines using sort array, top, bottom, topN or bottomN expressions in sub-pipelines.

“In clone(), ExpressionSortArray, ExpressionTopN, ExpressionTop, ExpressionBotton and ExpressionBottomN simply copy the PatternValueCmp _sortBy member.”

jira.mongodb.org

What to do

  1. Check whether your setup matches what the bug needs.

    Affects MongoDB Server builds that include SERVER-119491 (added in 9.0), which changed expression cloning.
  2. Upgrade to a fixed version: 9.0.7.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-120821 (Post-authentication use-after-free in MongoDB Server aggregation sub-pipelines), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120821 (entry last updated 2026-11-13):
Affected:
- MongoDB MongoDB Server: from 9.0.0, fixed in 9.0.7
Fixed versions: 9.0.7.
Conditions (all must be true for the bug to be hit):
- Affects MongoDB Server builds that include SERVER-119491 (added in 9.0), which changed expression cloning. (source: https://jira.mongodb.org/browse/SERVER-136285)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-120821 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120821 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://jira.mongodb.org/browse/SERVER-136285
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120821
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120821"}.

Affected versions

cve.now Index

32of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach17/20Affects MongoDB (a widely deployed server, runtime, framework or database)
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 82 if added to CISA KEV
  • Would score about 77 if CISA's SSVC rates exploitation active
  • Would score about 39 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now3 days
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 10Nov 22
  • EPSS: 0.41%
  • Posted on X by cve.now Nov 10

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkjira.mongodb.org · browse/SERVER-136285
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-120821
RecordNVD · CVE-2026-120821

Questions about CVE-2026-120821

Is CVE-2026-120821 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A use-after-free is a memory bug where a program keeps using memory it has already released. This flaw sits in how MongoDB Server handles aggregation sub-pipelines and requires the attacker to be logged in first.

Source: jira.mongodb.org

Which versions are affected by CVE-2026-120821?

MongoDB Server: from 9.0.0 before 9.0.7.

Source: cve.now feed data

Am I affected, and how do I check?

The product range listed is MongoDB Server from 9.0.0 up to 9.0.7, and the advisory ties the issue to builds that include the change SERVER-119491 introduced in 9.0. To check a build, run db.version() in the mongo shell or look at the version reported in the server log at startup.

Source: jira.mongodb.org

How do I fix CVE-2026-120821?

Upgrade MongoDB Server to 9.0.7, which is the listed fixed version. No patch identifiers or workaround are given in the checked facts.

Source: jira.mongodb.org

No corrections so far. Something wrong on this page? Report an error.