cve.bz

CVE-2026-120803 MongoDB SBE $locf Window Accumulator Use-After-Free Enables Heap OOB Read and Server Crash

7.1 highEPSS 0.4%

High (7.1) in mongodb mongodb server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
A use-after-free issue exists in MongoDB’s SBE (Slot-Based Execution) implementation of a window function accumulator used by certain $setWindowFields aggregation pipelines. Under specific conditions, the accumulator can retain a dangling pointer to memory that has since been freed. When this stale pointer is later dereferenced during serialization of the carried-forward value, it can result in a heap out-of-bounds read that may expose adjacent heap contents and crash the mongod server. An authenticated user with readWrite privileges on a database can trigger this issue by crafting a specific aggregation pipeline.

Severity

CVSS 4.0

7.1 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
Assigned by
mongodb (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-120803 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120803?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120803?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120803 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-120803

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-120803](https://cve.bz/cve/badge/CVE-2026-120803.svg)](https://cve.bz/cve/CVE-2026-120803)

HTML:

<a href="https://cve.bz/cve/CVE-2026-120803"><img src="https://cve.bz/cve/badge/CVE-2026-120803.svg" alt="CVE-2026-120803"></a>

Affected

  • mongodb:mongodb server

Versions

From the CNA's record in the CVE List.

ProductAffected
MongoDB Serverfrom 9.0.0 before 9.0.7
MongoDB Serverfrom 8.3.0 before 8.3.16

References

Check your stackJSON