# CVE-2026-114655: KMS request injection via unsanitized key vault and provider values in libmongocrypt


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114655, GHSA-7mvq-mg47-m88j, UBUNTU-CVE-2026-114655

## What is CVE-2026-114655?

CVE-2026-114655 is a medium-severity vulnerability in MongoDB libmongocrypt, published on 22 Oct 2026. 

### Official description

libmongocrypt builds requests to external key management services (AWS, Azure and GCP) by inserting values from key vault documents, KMS provider configuration and KMS responses into request lines, headers and signed request bodies without validating or encoding them for each context. A user with write access to the key vault collection can alter the structure of these requests, including adding members to request bodies and token claims that the library then signs with the application's credentials. This may result in key management operations being performed with parameters the application did not intend.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

Upgrade to a fixed version.

## Is CVE-2026-114655 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114655 is a medium-severity vulnerability in MongoDB libmongocrypt, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114655 in the wild and no public exploit code.

Affected product: MongoDB libmongocrypt. 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-114655/ (Markdown: https://insights.sbomify.com/CVE-2026-114655/index.md)
```

## Sources

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

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