Skip to main content
VulnerabilityPublished

CVE-2025-7259: MongoDB Server · Type Confusion

Affects MongoDB ServerSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 15:59 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 28% 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.1
  • =8.1.0
Fixed in–

AI-suggested

  1. Restrict database access strictly to trusted and necessary users, enforcing the principle of least privilege to minimize the number of authorized users who could exploit this vulnerability.
  2. Implement robust monitoring and anomaly detection on MongoDB query patterns to detect unusual queries, such as those containing duplicate _id fields, which may indicate exploitation attempts.
  3. Use network segmentation and firewall rules to limit access to MongoDB servers only from trusted application servers and administrative hosts.
  4. Regularly audit user privileges and revoke unnecessary or outdated access rights to reduce the risk of insider threats.
  5. Until an official patch is released, consider deploying MongoDB instances in high-availability configurations with failover capabilities to minimize downtime in case of crashes.
  6. Engage with MongoDB support or follow official advisories closely to apply patches or updates promptly once available.
  7. Conduct internal penetration testing and fuzzing focused on query inputs to identify and mitigate similar input validation issues proactively.

Description

An authorized user can issue queries with duplicate _id fields, that leads to unexpected behavior in MongoDB Server, which may result to crash. This issue can only be triggered by authorized users and cause Denial of Service. This issue affects MongoDB Server v8.1 version 8.1.0.

References

Community reviews

Loading reviews…