# CVE-2026-114653: Silent client-side encryption bypass via unescaped field-name regex in CSFLE schema builder


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/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:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-ggmm-wc43-vphh

## What is CVE-2026-114653?

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

### Official description

A client-side encryption schema construction component in the MongoDB C# Driver places caller-supplied field identifiers into a position that is interpreted as a pattern expression, without normalizing or validating them. As a result, an application that designates certain fields for client-side field-level encryption may have the protection silently fail to apply, so data intended to be encrypted is stored and returned in cleartext; conversely, the rule may apply more broadly than intended. No user action is required to cause the condition, and any party with ordinary read access to the stored data — without possession of the encryption keys — can observe the unprotected values.

Weakness: CWE-185 (Incorrect Regular Expression)

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


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

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

## Is CVE-2026-114653 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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