# CVE-2026-119672: mongofiles may disclose GridFS content to standard output through a stored filename


- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/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-vj7x-r9xp-w7fv, UBUNTU-CVE-2026-119672

## What is CVE-2026-119672?

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

### Official description

MongoDB Database Tools mongofiles uses a database-stored GridFS filename as the output destination for get_id when --local is not specified. A user who can modify the file metadata can set the stored filename to '-', causing a later authorized retrieval to write the file contents to standard output instead of a local file. If standard output is captured in a location accessible to that user, this may disclose GridFS content the user cannot read directly. Exploitation requires a higher-privileged operator to retrieve the affected file without an explicit local destination and attacker access to the captured output. This issue affects MongoDB Database Tools from version 3.1.4 through versions before 100.20.1.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-119672 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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