# CVE-2026-120819: Use-after-free in Wasm JS-BSON bridge lets read-only users read 24 KiB via $accumulator


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/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-89h3-wmrf-r95w

## What is CVE-2026-120819?

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

### Official description

A memory-management flaw in the server-side JavaScript execution component of MongoDB Server can allow an authenticated user holding only read privileges to cause the server to access memory that has already been released. By submitting a specially crafted database command that runs user-supplied JavaScript, the user can cause a bounded amount of adjacent process memory to be returned in the command's result. This results in the user obtaining information they are not authorized to access. Integrity and availability are not affected.

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2026-120819 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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