Skip to main content
VulnerabilityPublished

CVE-2025-6712: MongoDB Server · Uncontrolled Resource Consumption

Affects MongoDB ServerSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 10:12 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 26% 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 7 Jul 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

Affected software

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

AI-suggested

  1. Immediate mitigation should include upgrading MongoDB Server to version 8.0.10 or later once the patch is released by MongoDB Inc.
  2. Until a patch is available, organizations should restrict network access to MongoDB instances using firewalls, VPNs, or IP whitelisting to limit exposure to untrusted networks.
  3. Implement resource limits and monitoring on MongoDB servers to detect abnormal memory usage patterns early, enabling proactive response before crashes occur.
  4. Use MongoDB's built-in security features such as authentication and role-based access control (RBAC) to minimize the risk of unauthorized triggering of resource-intensive operations.
  5. Regularly review and optimize queries and workloads to avoid operations that could inadvertently cause excessive resource consumption.
  6. Employ infrastructure-level protections such as container resource limits or virtual machine memory caps to contain the impact of memory exhaustion.
  7. Maintain up-to-date backups and disaster recovery plans to ensure rapid restoration in case of service disruption. These steps go beyond generic advice by focusing on network exposure reduction, proactive monitoring, and operational best practices tailored to MongoDB environments.

Description

MongoDB Server may be susceptible to disruption caused by high memory usage, potentially leading to server crash. This condition is linked to inefficiencies in memory management related to internal operations. In scenarios where certain internal processes persist longer than anticipated, memory consumption can increase, potentially impacting server stability and availability. This issue affects MongoDB Server v8.0 versions prior to 8.0.10

References

Community reviews

Loading reviews…