Skip to main content
CVE-2025-12119VulnerabilityPublished Updated

CVE-2025-12119: MongoDB C Driver · Expired Pointer Dereference

Affects MongoDB C DriverSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 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-26.

What to do

Affected software

ProductAffectedFixed in
GitHubmongodb/mongo-c-driverpkg:github/mongodb/mongo-c-driverOther threatsAffected
  • =1.9.0
  • =2.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately identify and inventory all applications and services using the MongoDB C Driver versions 1.9.0 and 2.0.0. Until official patches are released, avoid passing large options to mongoc_bulk_operation_t calls or refactor code to minimize bulk operation complexity. Employ runtime memory protection tools such as AddressSanitizer or similar to detect invalid memory accesses during testing and staging. Restrict local access to systems running vulnerable software, enforce strict access controls, and monitor for unusual local activity indicative of exploitation attempts. Prepare for rapid patch deployment by establishing close communication with MongoDB vendor channels and subscribing to security advisories. Conduct code reviews focusing on bulk operation usage and memory management practices. Additionally, implement application-level logging and anomaly detection to identify potential exploitation attempts early. Once patches become available, prioritize their deployment in production environments. Consider isolating critical database clients in hardened containers or virtual machines to limit impact scope.

Description

A mongoc_bulk_operation_t may read invalid memory if large options are passed.

References

Community reviews

Loading reviews…