MongoDB Server sharding flaw lets shard admins act beyond scope
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Privilege escalation
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-250.
Summary
An improper privilege management issue in the sharding subsystem of MongoDB Server lets a user with certain shard-level administrative privileges have persisted internal coordination state reprocessed with elevated internal authority. Because that state is trusted rather than re-validated, operations can run beyond the user's authorized scope, including changes to cluster-wide security configuration. An attacker needs an authenticated session directly against a cluster member, and the flaw can lead to unauthorized access to and modification of data across the cluster. The weakness is classified as CWE-250.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| MongoDB | MongoDB Server | 9.0.0 to before 9.0.7; 8.3.0 to before 8.3.16; 8.0.0 to before 8.0.37 | 9.0.7, 8.3.16, 8.0.37 | Patch available | CNA |
- MongoDB Server VendorMongoDB Affected 9.0.0 to before 9.0.7; 8.3.0 to before 8.3.16; 8.0.0 to before 8.0.37 Fixed in 9.0.7, 8.3.16, 8.0.37 Patch available CNA
Remediation
Upgrade MongoDB Server to 9.0.7, 8.3.16, or 8.0.37, depending on the branch in use.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · CNA MongoDB Server (MongoDB) Fixed in 9.0.7, 8.3.16, 8.0.37
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
MongoDB Server 8.0.37, 8.3.16, 9.0.7
3 records Highest priority Priority LOW 3 LOW
Other records, highest priority first
- TI-2026-89283 Use-after-free read in MongoDB Server SBE engine during $unwindPriority LOW 27
- TI-2026-89293 Uncontrolled resource use in MongoDB Server causes denial of servicePriority LOW 24
Timeline
- 2026-11-10 Threatist record created from CVE-2026-120814
- 2026-11-10 Alias added: GHSA-4h4m-qr7q-h832
- 2026-11-12 Priority changed: MEDIUM → LOW
- 2026-11-13 CISA SSVC decision points changed
References
More MongoDB vulnerabilities
- TI-2019-08023 Remote code execution in mongo-express via toBSON endpoints KEVCVSS 3.1CRITICAL 9.9
- TI-2025-13542 Zlib header length mismatch in MongoDB Server allows memory read KEVCVSS 4.0HIGH 8.7
- TI-2026-89295 MongoDB Server Missing Authorization Check in Replication Administrative Command CVSS 4.0HIGH 8.6
- TI-2026-89289 Incorrect authorization in MongoDB Server allows admin access CVSS 4.0HIGH 8.6
- TI-2026-79432 BSON output corruption via out-of-range binary subtype in MongoDB C# Driver CVSS 4.0MEDIUM 6.9
- TI-2026-79424 NoSQL command injection via mismatched BSON length in MongoDB C# Driver CVSS 4.0MEDIUM 6.9
Sources
- CVE-2026-120814 · CVE Program
- CVE-2026-120814 · NVD
- FIRST EPSS
- GHSA-4h4m-qr7q-h832 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences