# CVE-2026-120684: MongoDB C Driver GridFS gap lets a shared writer recover a protected client's password


- **Severity:** Medium 6.0 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120684, UBUNTU-CVE-2026-120684

## What is CVE-2026-120684?

CVE-2026-120684 is a medium-severity vulnerability in MongoDB C Driver, published on 3 Nov 2026. 

### Official 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.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2026-120684?


## How do I fix CVE-2026-120684?

Upgrade to a fixed version.

## Is CVE-2026-120684 being exploited?

There is no known exploitation of CVE-2026-120684 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120684 and fix it if it is affected.

What it is: CVE-2026-120684 is a medium-severity vulnerability in MongoDB C Driver, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120684 in the wild and no public exploit code.

Affected product: MongoDB C Driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120684/ (Markdown: https://insights.sbomify.com/CVE-2026-120684/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120684
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120684
- OSV: https://osv.dev/vulnerability/CVE-2026-120684

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120684/
Summaries are generated and may contain mistakes; the official description above is the record.
