Medium · published August 11, 2026
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.
| Product | Versions | Fixed in |
|---|---|---|
| mongodb/mongodb | ≥ 7.0.0, < 7.0.40 | 7.0.40 |
| mongodb/mongodb | ≥ 8.0.0, < 8.0.29 | 8.0.29 |
| mongodb/mongodb | ≥ 8.2.0, ≤ 8.2.12 | — |
| mongodb/mongodb | ≥ 8.3.0, < 8.3.8 | 8.3.8 |
| mongodb/mongodb | all versions | — |
| mongodb/mongodb | all versions | — |
| mongodb/mongodb | all versions | — |