# CVE-2026-114652: Update operator injection via single-element list rewriting in the update builder


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-7gfh-w7g4-x3p9

## What is CVE-2026-114652?

CVE-2026-114652 is a high-severity vulnerability in MongoDB C# Driver, published on 22 Oct 2026. 

### Official description

A data-query-logic neutralization weakness in the update-statement construction component of the MongoDB C# Driver can cause application-supplied values to be interpreted as query/update logic rather than as literal data. An application user who can influence the content of values that the application passes into the affected builder surface, without any special privilege beyond ordinary read-write application access, may cause stored data to be modified or removed in ways the application never intended. The result is unauthorized integrity impact on the affected application data; there is no direct loss of confidentiality or availability of the database service.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

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

## Is CVE-2026-114652 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114652 is a high-severity vulnerability in MongoDB C# Driver, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114652 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-114652/ (Markdown: https://insights.sbomify.com/CVE-2026-114652/index.md)
```

## Sources

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

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