# CVE-2026-114648: NoSQL injection via dot and dollar characters in LINQ filter field names and dictionary keys


- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:H/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-2xqr-fxmx-2cmf

## What is CVE-2026-114648?

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

### Official description

The MongoDB C# Driver does not neutralize dot and dollar characters in dictionary keys, field names and array-filter identifiers used in LINQ queries before placing them into the field paths it sends to the server. An application user whose input reaches these positions can redirect a query or update to fields the application did not name, which can expose other users' documents and widen updates beyond the intended data. Certain values can also write malformed fields that leave stored documents unreadable by the application until they are repaired.

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

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


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

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

## Is CVE-2026-114648 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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