# CVE-2026-120809: Heap use-after-free read via yield-time state save in time-series block unpacking


- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/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-3x8p-q9c8-5g87

## What is CVE-2026-120809?

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

### Official description

A use-after-free read issue exists in MongoDB’s SBE (Slot-Based Execution) engine when processing aggregation pipelines with $unwind on time-series collections. An internal error in state-preservation logic can cause a value still referenced by downstream stages to have its underlying memory freed prematurely. An authenticated user can craft an aggregation pipeline under specific conditions to trigger this condition, potentially reading recycled server heap memory in query results or crashing the server. This issue is only triggerable when a non-default server parameter related to the SBE engine is enabled.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2026-120809 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120809 is a medium-severity vulnerability in MongoDB Server, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120809 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-120809/ (Markdown: https://insights.sbomify.com/CVE-2026-120809/index.md)
```

## Sources

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

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