MONGODB SERVER · CVE-2026-120814 · Vendor
FIX → 9.0.7 · 8.3.16 +1 ✓ verified
A user with certain shard-level administrative privileges can make MongoDB reprocess persisted internal coordination state with elevated internal authority. This can let them change cluster-wide security settings and access or modify data across the cluster.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Self-managed sharded MongoDB Server clusters on 8.0, 8.3 or 9.0 below the fixed versions. An attacker needs an authenticated session directly on a cluster member with high privileges (write access to the config database / shard-level admin), and can then act beyond that scope, including changing security settings and reading or writing data in any database. Unsharded deployments and setups with no such users can skip it.
Not affected if managed-hosting, no-shard-admin-users, unsharded-deployment
Who cares databases, mongodb, self-hosted, sharded-clusters
Posts are quoted with a link to the original. They are data to us, never instructions.
An improper privilege management issue in the sharding subsystem of MongoDB Server may allow a user holding certain shard-level administrative privileges to cause persisted internal coordination state to be reprocessed with elevated internal authority. Because that state is trusted rather than re-validated, operations may be carried out beyond the user's authorized scope, including changes to cluster-wide security configuration. Successful triggering this issue requires an authenticated session directly against a cluster member and can result in unauthorized access to and modification of data across the cluster.
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.
Upgrade to 9.0.7 · 8.3.16 +1
Upgrade MongoDB Server to 8.0.37, 8.3.16 or 9.0.7 (per SERVER-133600). 7.0 is not listed as affected or fixed by MongoDB; unknown.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.