CVE-2026-119674: mongorestore may restore encoded collection names into an unintended collection
MongoDB · Database Tools
Fixed in 100.20.1 · Affected: MongoDB Database Tools before 100.20.1 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 5% of scored CVEs
DescriptionCVE.org
MongoDB Database Tools mongorestore incorrectly URL-decodes an original collection name read from metadata when the corresponding dump filename has been truncated. A database user who can create and populate a suitably encoded collection can cause a later authorized directory restore to write those documents into a different collection that the user cannot modify directly. When both collection names resolve to the same destination, backed-up documents may be omitted; use of --drop can also replace the unintended destination collection. Exploitation requires an operator to restore the affected collection from a directory dump with write access to the destination. This issue affects MongoDB Database Tools versions 100.0.2 through versions before 100.20.1.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- MongoDB · Database Toolsfrom 100.0.2 before 100.20.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- MongoDB
- Published
- November 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-119674 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.