# CVE-2026-113870: Improper Encoding of Server-Supplied JavaScript Values in MongoDB Compass BSON Parsing


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-pf8m-jx52-cwh3

## What is CVE-2026-113870?

CVE-2026-113870 is a high-severity vulnerability in MongoDB Compass, published on 21 Oct 2026. 

### Official description

MongoDB Compass improperly escapes certain BSON values when converting a stored view’s aggregation pipeline into editable source. When a user connects to a MongoDB deployment containing a specially crafted view and opens that view for editing, the values can cause arbitrary code to execute with the privileges of the user running Compass.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

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


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

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

## Is CVE-2026-113870 being exploited?

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

Public exploit code:

- Offline Python detector for CVE-2026-113870 exposure in MongoDB Compass inventories, with CSV/JSON input and auditable reports. (github_poc): https://github.com/mehmet-emir-eroglu/CVE-2026-113870

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113870 is a high-severity vulnerability in MongoDB Compass, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113870 in the wild and no public exploit code.

Affected product: MongoDB Compass. 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-113870/ (Markdown: https://insights.sbomify.com/CVE-2026-113870/index.md)
```

## Sources

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

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