published 11 Aug 2026 · updated 11 Aug 2026
Missing Authorization in MongoDB Sharded Transaction Commit/Abort Handling Leads to Cross-Shard Data Inconsistency
6.4MediumCVSS 6.4EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Server 7.0.40, Server 8.0.29 and Server 8.3.8.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| MongoDB | Server | >=7.0 <7.0.40, >=8.0 <8.0.29, >=8.3.0 <8.3.8 | 7.0.40, 8.0.29, 8.3.8 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in MongoDB, strongest first
10.0CriticalPublic exploit
10.0CriticalCISA KEVPublic exploit
10.0CriticalCISA KEVPublic exploit
Embed
A live severity badge for an advisory, README or ticket