# CVE-2026-120814: MongoDB Server privilege escalation in sharding subsystem

Source: https://junglewise.ai/threats/cve-2026-120814-an-improper-privilege-management-issue-in-the-sharding-subsystem  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-120814 · Severity: high · CVSS 7.2 · Published 2026-11-10

MongoDB Server's sharding subsystem contains a privilege management flaw that allows authenticated users with shard-level administrative permissions to execute operations beyond their authorized scope, including modifications to cluster-wide security settings. An attacker exploiting this vulnerability could gain unauthorized access to and modify data across the entire MongoDB cluster.

Technologies: [MongoDB Server](https://junglewise.ai/threats/technologies/mongodb-server). Vendors: [MongoDB](https://junglewise.ai/threats/vendors/mongodb).

## Quick answers

**Is CVE-2026-120814 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-120814 being exploited in the wild.

**How severe is CVE-2026-120814?** High severity, with a CVSS score of 7.2, published 10 November 2026.

**Which products and versions are affected?** MongoDB Server Prior to 8.3.16, 9.0.7, and 8.0.37.

**Is there a fix for CVE-2026-120814?** Yes: fixed in 8.3.16, 9.0.7, 8.0.37. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-120814 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-120814?** Check whether you run MongoDB Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 8.3.16, 9.0.7, 8.0.37

## Technical details

An improper privilege management issue in MongoDB's sharding subsystem allows reprocessing of persisted internal coordination state with elevated internal authority without re-validation. Users holding shard-level administrative privileges can abuse this to carry out operations beyond their authorized scope, including cluster-wide security configuration changes. The attack requires an authenticated session directly against a cluster member.

## Affected products

- MongoDB MongoDB Server Prior to 8.3.16, 9.0.7, and 8.0.37

## Timeline

- 2026-11-10: disclosed
- 2026-11-10: patched

## References

- [https://jira.mongodb.org/browse/SERVER-133600](https://jira.mongodb.org/browse/SERVER-133600)

## Related threats

- [MongoDB Server authorization bypass in aggregation pipeline](https://junglewise.ai/threats/cve-2026-120825-an-authorization-weakness-in-the-aggregation-framework-of)
- [MongoDB Server use-after-free in time-series bucket validation](https://junglewise.ai/threats/cve-2026-120824-a-use-after-free-in-the-time-series-collection-component-of)
- [MongoDB Server missing authorization check in aggregation framework](https://junglewise.ai/threats/cve-2026-120823-a-missing-authorization-check-in-the-aggregation-framework-of)
- [MongoDB Server authorization bypass in applyOps](https://junglewise.ai/threats/cve-2026-120822-mongodb-server-may-omit-an-authorization-check-on-the-resource)
- [MongoDB Server use-after-free in aggregation framework](https://junglewise.ai/threats/cve-2026-120821-a-use-after-free-in-the-aggregation-framework-of-mongodb-server)