# CVE-2026-119673: mongofiles may write outside the working directory through a symlink


- **Severity:** Low 1.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:P/VC:N/VI:L/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-3jx2-r7fh-fm2g, UBUNTU-CVE-2026-119673

## What is CVE-2026-119673?

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

### Official description

MongoDB Database Tools mongofiles does not resolve existing parent-directory symlinks when validating output paths for get_regex. An unauthorized user who can both upload a GridFS file and place a symlink in the operator's download working directory can cause a later retrieval to create a file containing unauthorized user-controlled data outside that directory, using the operator process's filesystem permissions. The issue can occur with default traversal and overwrite settings. Exploitation requires an operator to retrieve matching files from the affected working directory; the demonstrated default behavior creates a new file rather than overwriting an existing file. This issue affects MongoDB Database Tools versions 100.2.0 through versions before 100.20.1.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-119673 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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