Quick answers
- Is CVE-2026-114655 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114655 being exploited in the wild.
- How severe is CVE-2026-114655?
- Medium severity, with a CVSS score of 5.9, published 22 October 2026.
- Which products and versions are affected?
- MongoDB Libmongocrypt before 1.21.1.
- Is there a fix for CVE-2026-114655?
- Yes: fixed in 1.21.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-114655 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114655?
- Check whether you run MongoDB Libmongocrypt at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.21.1
Technical details
libmongocrypt constructs HTTP requests to external key management services by interpolating values from key vault documents, KMS provider configuration, and KMS responses directly into request lines, headers, and signed bodies without validation or encoding. An authenticated attacker with write access to the key vault collection can alter these values to modify request structure and add members to request bodies or signed token claims, causing the library to send requests with parameters the application did not authorize.
Affected products
- MongoDB libmongocrypt before 1.21.1
Timeline
- 2026-10-22: disclosed