CVE-2026-120684

MongoDB C Driver GridFS gap lets a shared writer recover a protected client's password

  • Medium 6.5

Description

A memory-initialization flaw in the legacy GridFS file handling of the MongoDB C Driver can cause uninitialized process memory to be treated as valid file content and stored on the server. A database user holding ordinary write access to a shared storage area can arrange conditions under which an application later appends to such a file and writes that memory into records the same user is permitted to read, which may result in unintended disclosure of sensitive information from the application's process, including credentials.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
mongodb
EPSS
0.322% likely to be exploited in the next 30 days, higher than 25.571% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.0CVSS 4.0, Mediumfrom the CNA (mongodb)CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • 6.5CVSS 3.1, Mediumfrom the CNA (mongodb)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
MongoDBC Driver
  • Default status: unaffected
  • 1.25.0 up to and including 1.30.14 (affected)
  • 2.0.0 up to and including 2.5.7 (affected)

Timeline

  1. 3 Nov 2026 Published

Weakness

References