# CVE-2026-120818: Use-After-Free in MongoDB Server JavaScript Support for Aggregation Leads to Information Disclosure


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/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-xcr7-38c4-884c

## What is CVE-2026-120818?

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

### Official description

A use-after-free weakness in MongoDB Server's server-side JavaScript support for aggregation may allow a stale reference to previously freed process memory to be read and returned. An authenticated user with minimal or no assigned roles can trigger this condition over the normal network protocol by submitting a single crafted aggregation request, with no additional privileges or non-default configuration. Successful triggering this issue may result in adjacent process memory contents being returned, including data that undermines memory-layout randomization, and may in some cases affect server availability.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2026-120818 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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