CVE-2026-114655: MongoDB libmongocrypt · Injection
Affects MongoDB libmongocryptSource CVE Database V5
Not known to be exploited · CVSS 6.0 Medium : upgrade to 1.21.1 when convenient.
Data as of 26 Oct 2026, 14:18 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.21.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade libmongocrypt and mongodb/libmongocrypt to 1.21.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDBlibmongocrypt | Affected
| Fixed in
|
GitHubmongodb/libmongocryptpkg:github/mongodb/libmongocryptOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available for libmongocrypt versions affected by this vulnerability. Users should upgrade to version 1.21.1 or later to remediate the issue. For cloud-hosted services using libmongocrypt, the vendor manages remediation server-side; users should consult the vendor advisory for confirmation and further guidance.
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.