# CVE-2026-106430: Query and rename target confusion via embedded NUL truncation in MongoDB C++ Driver

> An authenticated attacker can manipulate field or collection names to cause the application to read or modify unintended data due to NUL byte truncation.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-106430, UBUNTU-CVE-2026-106430

## What is CVE-2026-106430?

CVE-2026-106430 is a medium-severity vulnerability in MongoDB C++ Driver, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The MongoDB C++ Driver discards content after an embedded NUL byte in certain field and collection names accepted by the collection API. This can cause the driver and the calling application to interpret the same name differently. An authenticated actor who can influence a name passed by an affected application can cause the application to read distinct values from an unintended field or rename an unintended collection. These operations use the application's existing database credentials.

Weakness: CWE-436 (Interpretation Conflict)

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


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

Apply the vendor's patch.

## Is CVE-2026-106430 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106430 is a medium-severity vulnerability in MongoDB C++ Driver, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-106430 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-106430/ (Markdown: https://insights.sbomify.com/CVE-2026-106430/index.md)
```

## Sources

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

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