Skip to main content
VulnerabilityPublished

CVE-2025-12657: MongoDB Server · Unchecked Error Condition

Affects MongoDB ServerSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 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 26 Oct 2026.

What to do

Affected software

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

AI-suggested

  1. Restrict network access to KMIP services on MongoDB servers by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts only.
  2. Monitor KMIP traffic for malformed or anomalous packets using intrusion detection systems or custom logging to detect potential exploitation attempts early.
  3. Enforce strong authentication and access controls to minimize the risk of privileged credential compromise.
  4. Apply strict input validation and sanitization at the application or proxy level if possible to filter malformed KMIP packets before they reach MongoDB.
  5. Prepare for timely patching by tracking MongoDB vendor advisories and testing updates in staging environments as soon as patches become available.
  6. Conduct regular security audits and penetration testing focused on KMIP and MongoDB configurations to identify and remediate weaknesses.
  7. Consider deploying MongoDB in high-availability configurations to mitigate downtime impact from potential crashes.
  8. Educate administrators and security teams about this vulnerability and the importance of monitoring KMIP-related activities.

Description

The KMIP response parser built into mongo binaries is overly tolerant of certain malformed packets, and may parse them into invalid objects. Later reads of this object can result in read access violations.

References

Community reviews

Loading reviews…