Skip to main content
CVE-2025-10060VulnerabilityPublished

CVE-2025-10060: MongoDB Server · Operation on a Resource after Expiration or Release

Affects MongoDB ServerSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Sep 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
MongoDB Inc MongoDB ServerAffected
  • =6.0
  • =7.0
  • =8.0
Fixed in–

AI-suggested

European organizations should prioritize upgrading MongoDB Server to the fixed versions: 6.0.25 or later for the 6.0 series, 7.0.22 or later for the 7.0 series, and 8.0.12 or later for the 8.0 series. Until upgrades are applied, organizations should audit and review transactional code that performs upsert operations with retries to minimize triggering the unique index constraint violation. Implementing stricter access controls to limit privileges to only necessary users can reduce the risk of exploitation. Monitoring MongoDB server logs for unusual transaction failures or crashes can provide early warning signs of attempted exploitation. Additionally, organizations should ensure robust backup and recovery procedures are in place to mitigate the impact of potential server crashes. Where possible, testing transactional workloads in staging environments after applying patches can validate stability. Network-level protections such as firewall rules restricting access to MongoDB instances and employing authentication mechanisms can further reduce exposure. Finally, staying informed through MongoDB security advisories and applying patches promptly is critical.

Description

MongoDB Server may allow upsert operations retried within a transaction to violate unique index constraints, potentially causing an invariant failure and server crash during commit. This issue may be triggered by improper WriteUnitOfWork state management. This issue affects MongoDB Server v6.0 versions prior to 6.0.25, MongoDB Server v7.0 versions prior to 7.0.22 and MongoDB Server v8.0 versions prior to 8.0.12

References

Community reviews

Loading reviews…