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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://jira.mongodb.org/browse/SERVER-130544 Vendor Advisory, Issue Tracking
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.9 · mongodbNVD modified 2026-10-23 21:10
Affected (CPE criteria) 4
cpe:2.3:a:mongodb:mongodb:*:*:*:*:*:*:*:*cpe:2.3:a:mongodb:mongodb:9.0.0:alpha0:*:*:-:-:*:*cpe:2.3:a:mongodb:mongodb:9.0.0:alpha1:*:*:-:-:*:*cpe:2.3:a:mongodb:mongodb:9.1.0:alpha0:*:*:-:-:*:*
References 1
- https://jira.mongodb.org/browse/SERVER-130544 Vendor Advisory, Issue Tracking