# CVE-2026-119674: mongorestore may restore encoded collection names into an unintended collection


- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** GHSA-px68-pqg4-8q7x, UBUNTU-CVE-2026-119674

## What is CVE-2026-119674?

CVE-2026-119674 is a low-severity vulnerability in MongoDB Database Tools, published on 3 Nov 2026. 

### Official description

MongoDB Database Tools mongorestore incorrectly URL-decodes an original collection name read from metadata when the corresponding dump filename has been truncated. A database user who can create and populate a suitably encoded collection can cause a later authorized directory restore to write those documents into a different collection that the user cannot modify directly. When both collection names resolve to the same destination, backed-up documents may be omitted; use of --drop can also replace the unintended destination collection. Exploitation requires an operator to restore the affected collection from a directory dump with write access to the destination. This issue affects MongoDB Database Tools versions 100.0.2 through versions before 100.20.1.

Weakness: CWE-174 (Double Decoding of the Same Data)

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


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

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

## Is CVE-2026-119674 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119674 is a low-severity vulnerability in MongoDB Database Tools, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119674 in the wild and no public exploit code.

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

## Sources

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

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