Skip to main content
CVE-2025-6706VulnerabilityPublished

CVE-2025-6706: MongoDB Server · Use After Free

Affects MongoDB ServerSource CVE Database V5

0

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 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

1. Immediate upgrade to MongoDB Server versions 6.0.21, 7.0.17, or 8.0.4 (or later) once patches are released to address this vulnerability. 2. Restrict and audit authenticated user access to MongoDB instances, enforcing the principle of least privilege to minimize the number of users who can execute aggregation operations. 3. Monitor MongoDB logs for unusual or complex aggregation pipeline queries that could indicate exploitation attempts. 4. Disable or restrict the use of the SBE engine if feasible, or apply configuration hardening to limit exposure until patches are applied. 5. Implement network segmentation and firewall rules to limit access to MongoDB servers only to trusted hosts and users. 6. Regularly review and update authentication mechanisms, including enforcing strong credentials and multi-factor authentication for database access. 7. Prepare incident response plans to quickly identify and mitigate potential DoS events caused by this vulnerability.

Description

An authenticated user may trigger a use after free that may result in MongoDB Server crash and other unexpected behavior, even if the user does not have authorization to shut down a server. The crash is triggered on affected versions by issuing an aggregation framework operation using a specific combination of rarely-used aggregation pipeline expressions. This issue affects MongoDB Server v6.0 version prior to 6.0.21, MongoDB Server v7.0 version prior to 7.0.17 and MongoDB Server v8.0 version prior to 8.0.4 when the SBE engine is enabled.

References

Community reviews

Loading reviews…