# CVE-2026-114643: Duplicate geometry fields via unvalidated GeoJSON extra members


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/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-mqvm-xxqr-vqw5

## What is CVE-2026-114643?

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

### Official description

The MongoDB C# Driver writes GeoJSON extra members without checking whether their names collide with reserved GeoJSON members such as type and coordinates. An application that places user-supplied field names into these extra members can store documents with duplicate geometry fields, so the server and the driver resolve different values for the same record. Affected records can also become unreadable through the driver, interrupting application code that reads them.

Weakness: CWE-694 (Use of Multiple Resources with Duplicate Identifier)

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


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

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

## Is CVE-2026-114643 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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