# CVE-2026-120811: Use-After-Free in MongoDB Server Classic Query Engine Plan Cache Leads to Information Disclosure and Denial of Service


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:L/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-3r42-9858-556g

## What is CVE-2026-120811?

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

### Official description

A use-after-free issue exists in the MongoDB server’s classic query engine plan cache. Under certain query conditions, an unowned reference to data from an earlier command can be retained in cached plan statistics. After the originating memory is freed, a subsequent diagnostic command serializing those statistics can read freed heap memory, potentially returning sensitive server process memory contents to the authenticated client. Under certain heap reuse conditions, this may also cause the server to crash.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2026-120811 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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