Skip to main content
CVE-2025-13644VulnerabilityPublished

CVE-2025-13644: MongoDB Server · Reachable Assertion

Affects MongoDB ServerSource CVE Database V5

0

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

Data as of 25 Oct 2026, 19:02 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 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.1.2, 8.0.13, 7.0.26
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 25 Nov 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-25.

What to do

Upgrade MongoDB Server to 8.1.2, 8.0.13 or 7.0.26.

Affected software

ProductAffectedFixed in
MongoDB Inc. MongoDB ServerAffected
  • =8.0
  • =7.0
  • =8.1
  • <7.0.26
  • <8.0.13
  • <8.1.2
Fixed in
  • 7.0.26
  • 8.0.13
  • 8.1.2

AI-suggested

European organizations should prioritize upgrading MongoDB Server to the fixed versions 7.0.26, 8.0.13, or 8.1.2 as soon as possible to eliminate this vulnerability. If you cannot patch yet, organizations should implement strict access controls to limit who can perform batched delete operations, ideally restricting this capability to trusted administrators only. Network segmentation and firewall rules should be enforced to restrict access to MongoDB instances, minimizing exposure to potentially malicious actors. Monitoring and alerting should be enhanced to detect abnormal batched delete requests or server crashes indicative of exploitation attempts. Additionally, organizations should review and harden their MongoDB configurations, disabling unnecessary features and enabling audit logging to track delete operations. Regular backups and tested recovery procedures are essential to minimize downtime in case of crashes. Finally, educating internal teams about the risk and signs of exploitation can improve incident response readiness.

Description

MongoDB Server may experience an invariant failure during batched delete operations when handling documents. The issue arises when the server mistakenly assumes the presence of multiple documents in a batch based solely on document size exceeding BSONObjMaxSize. This issue affects MongoDB Server v7.0 versions prior to 7.0.26, MongoDB Server v8.0 versions prior to 8.0.13, and MongoDB Server v8.1 versions prior to 8.1.2

References

Community reviews

Loading reviews…