cve.bz

CVE-2026-120814 MultiUpdateCoordinator state replay lets a shard administrator create a persistent cluster root user

7.5 highEPSS 0.4%

High (7.5) in mongodb mongodb server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.5 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-250 Execution with Unnecessary Privileges
Published
Modified
Assigned by
mongodb (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-120814 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120814?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120814?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120814 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-120814

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-120814](https://cve.bz/cve/badge/CVE-2026-120814.svg)](https://cve.bz/cve/CVE-2026-120814)

HTML:

<a href="https://cve.bz/cve/CVE-2026-120814"><img src="https://cve.bz/cve/badge/CVE-2026-120814.svg" alt="CVE-2026-120814"></a>

Affected

  • mongodb:mongodb server

Versions

From the CNA's record in the CVE List.

ProductAffected
MongoDB Serverfrom 9.0.0 before 9.0.7
MongoDB Serverfrom 8.3.0 before 8.3.16
MongoDB Serverfrom 8.0.0 before 8.0.37

Attack patterns (CAPEC)

  • CAPEC-69 Target Programs with Elevated Privileges Likelihood: High · Severity: Very High
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON