---
id: "CVE-2026-119675"
kind: "vulnerability"
aliases: ["CVE-2026-119675"]
title: "MongoDB Database Tools: mongorestore can create unauthorized root database accounts"
severity: "high"
cvss: 8.6
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["database-tools", "mongodb", "mongorestore", "package"]
not_affected_if: ["no-user-management-credentials", "trusted-dumps-only"]
published_at: "2026-11-03T17:18:07+00:00"
first_seen_at: "2026-11-03T17:21:56+00:00"
updated_at: "2026-11-03T17:23:59+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119675", "first_seen_at": "2026-11-03T17:21:56+00:00"}]
---

# MongoDB Database Tools: mongorestore can create unauthorized root database accounts

A crafted collection name in an untrusted database dump can make mongorestore bypass its guards and create a database user the operator did not choose, including one with the root role. An attacker who supplies the dump can then log in to the destination database with that account.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `mongorestore --version` and compare against the affected range
- Look for restores of dumps from untrusted sources in your backup or restore scripts
- List database users on the destination deployment for accounts you did not create

## Fix

- MongoDB Database Tools: upgrade to `100.20.1` or later

## Timeline

- 2026-11-03T17:21:56+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119675

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_