CVE-2026-120805 · Runtime
NO FIX YET
An authenticated user who has insert rights on one collection can craft a command with special encryption parameters so that internal Queryable Encryption metadata writes land on other encrypted collections in the same database. The attacker can corrupt encrypted index state and compaction operations for those collections.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running self-managed MongoDB Server that use Queryable Encryption and have users with insert privileges on at least one collection are the exposed group. Deployments that do not use Queryable Encryption, or where all users are fully trusted, are less exposed. The sources do not list affected or fixed versions.
Not affected if auth-required, no-queryable-encryption
Who cares mongodb, queryable-encryption, self-hosted
Unknown from the sources.
No fix yet, per the sources.
In MongoDB Server, an authenticated user with insert privileges on a collection could craft a command with specially constructed encryption-related parameters to redirect internal Queryable Encryption metadata writes to metadata belonging to other encrypted collections within the same database. The server’s authorization layer validated only the user-facing target collection namespace, while subsequent internal writes derived from client-supplied parameters were performed with elevated internal privileges, bypassing the original caller’s permission scope. This could allow unauthorized writes into another collection’s Queryable Encryption metadata, potentially corrupting encrypted index state and compaction operations.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.