Skip to main content
CVE-2025-14345VulnerabilityPublished

CVE-2025-14345: MongoDB Server · Improper Locking

Affects MongoDB ServerSource CVE Database V5

0

Not known to be exploited · CVSS 4.2 Medium · fixed in 8.2.2 : update MongoDB Server when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.2.2, 8.0.16, 7.0.26
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade MongoDB Server to 8.2.2, 8.0.16 or 7.0.26.

Affected software

ProductAffectedFixed in
MongoDB Inc.MongoDB ServerAffected
  • >=7.0 <7.0.26
  • >=8.0 <8.0.16
  • >=8.2 <8.2.2
Fixed in
  • 8.2.2
  • 8.0.16
  • 7.0.26

AI-suggested

European organizations should implement the following specific mitigation steps: 1) Immediately inventory MongoDB deployments to identify affected versions (7.0 prior to 7.0.26, 8.0 prior to 8.0.16, and 8.2 prior to 8.2.2). 2) Prioritize patching to the latest MongoDB versions where the flaw is fixed as soon as vendor patches become available. 3) Until patches are applied, restrict access to MongoDB instances to trusted users only, minimizing the risk of post-authentication exploitation. 4) Review and tighten authentication and authorization controls to limit privileges that can initiate cross-shard transactions. 5) Monitor transaction logs and application behavior for anomalies indicative of inconsistent transaction states. 6) Implement additional application-level consistency checks or compensating transactions to detect and correct inconsistencies. 7) Engage in thorough testing of transaction workflows post-patching to ensure integrity is restored. 8) Maintain up-to-date backups and disaster recovery plans to recover from potential data corruption. These steps go beyond generic advice by focusing on the specific nature of the vulnerability and its operational context.

Description

A post-authentication flaw in the network two-phase commit protocol used for cross-shard transactions in MongoDB Server may lead to logical data inconsistencies under specific conditions which are not predictable and exist for a very short period of time. This error can cause the transaction coordination logic to misinterpret the transaction as committed, resulting in inconsistent state on those shards. This may lead to low integrity and availability impact. This issue impacts MongoDB Server v8.0 versions prior to 8.0.16, MongoDB Server v7.0 versions prior to 7.0.26 and MongoDB server v8.2 versions prior to 8.2.2.

References

Community reviews

Loading reviews…