# CVE-2026-120673: Rust Driver 3.9.1 exports CSFLE plaintext in `db.query.text` before encrypting the command


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 3 Nov 2026

## What is CVE-2026-120673?

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

### Official description

A component of the MongoDB Rust Driver that records diagnostic tracing data can capture command content before automatic client-side field level encryption is applied. In deployments that turn on the optional tracing capability together with automatic in-use encryption, a party with read access to the application's exported trace data may obtain field values that the application designated for encryption, without access to the encryption keys. This may result in unintended disclosure of data.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

No fix has been published for CVE-2026-120673 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120673 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: MongoDB Rust 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-120673/ (Markdown: https://insights.sbomify.com/CVE-2026-120673/index.md)
```

## Sources

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

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