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


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-xqmg-xhh6-75p8

## What is CVE-2026-120803?

CVE-2026-120803 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-120803?


## How do I fix CVE-2026-120803?

No fix has been published for CVE-2026-120803 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120803 being exploited?

There is no known exploitation of CVE-2026-120803 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120803 and fix it if it is affected.

What it is: CVE-2026-120803 is a high-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120803 in the wild and no public exploit code.

Affected product: MongoDB Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120803/ (Markdown: https://insights.sbomify.com/CVE-2026-120803/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120803
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120803
- OSV: https://osv.dev/vulnerability/CVE-2026-120803

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120803/
Summaries are generated and may contain mistakes; the official description above is the record.
