EUVD-2026-56883
GHSA-g2m8-vcxw-5h4c
Severity by source
CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/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
Adjacent-network vector and PR:L for required authentication; S:C chosen because cross-shard integrity corruption extends impact beyond the directly targeted shard.
Primary rating from Vendor (mongodb).
CVSS VectorVendor: mongodb
Lifecycle Timeline
3DescriptionCVE.org
An issue in MongoDB Server could allow an authenticated user with direct network access to a shard to improperly commit or abort an in-progress prepared transaction, bypassing the intended transaction coordination process. This could result in cross-shard data inconsistency, cluster clock corruption, and violation of transaction atomicity guarantees.
AnalysisAI
MongoDB Server's sharded cluster transaction coordination is vulnerable to an authorization bypass that allows an authenticated, low-privileged user with direct adjacent-network access to a shard process to illegitimately commit or abort in-progress prepared transactions - actions that are normally reserved for the designated transaction coordinator. Exploitation can produce cross-shard data inconsistency, cluster clock corruption, and broken atomicity guarantees across the distributed database. No public exploit code exists and SSVC confirms no active exploitation; however, successful abuse could silently corrupt application-layer data integrity across the cluster.
Technical ContextAI
MongoDB sharded clusters implement multi-document ACID transactions via a two-phase commit protocol. A transaction coordinator (typically a mongos or config server) manages the 'prepare' and 'commit/abort' lifecycle across participating shards. Each shard exposes internal RPC endpoints used by the coordinator. CWE-862 (Missing Authorization) identifies the root cause: these shard-level transaction state endpoints fail to verify that the caller is the legitimate coordinator, rather than any authenticated network principal. An attacker exploiting this gap bypasses the intended coordinator-only authorization gate. Affected products per CPE (cpe:2.3:a:mongodb:mongodb_server:*:*:*:*:*:*:*:*) span MongoDB Server major lines 7.0, 8.0, and 8.3 prior to their respective patch releases.
RemediationAI
Upgrade MongoDB Server to 8.3.8 or later (for 8.3.x deployments), 8.0.29 or later (for 8.0.x deployments), or 7.0.40 or later (for 7.0.x deployments) - these are the vendor-confirmed fix versions per EUVD-2026-56883. As a compensating control if immediate patching is not possible, enforce network-layer access controls (firewall rules, security groups, or MongoDB's built-in IP allow-listing) to restrict access to shard ports (default 27018) exclusively to known mongos and config server IP addresses. This mitigation is highly effective because the vulnerability requires direct adjacent-network access to shard processes rather than the mongos tier; blocking unauthorized shard access eliminates the attack surface without affecting normal application traffic routed through mongos. Additionally, ensure all database accounts operating in the cluster context hold the minimum required privilege level and audit any accounts with unexpectedly broad network reach to internal shard endpoints. Patch details are referenced at https://jira.mongodb.org/browse/SERVER-130544.
MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMo
The find prototype in scripting/engine_v8.h in MongoDB 2.4.0 through 2.4.4 allows remote authenticated users to cause a
The MongoDB bson JavaScript module (also known as js-bson) versions 0.5.0 to 1.0.x before 1.0.5 is vulnerable to a Regul
Remote code execution in Chartbrew versions prior to 4.8.1 allows authenticated attackers with high privileges to execut
After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated user's
The default configuration for MongoDB before 2.3.2 does not validate objects, which allows remote authenticated users to
SimStudio below 0.5.74 has a missing authorization on MongoDB tool endpoints that allows attackers to execute arbitrary
MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are calle
MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of e
Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which ma
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. Rated critical severity (CVSS 9.8
Memory corruption in the MongoDB BI Connector ODBC Driver (fixed in v1.4.9) occurs when an oversized catalog, schema, or
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today