CVE-2026-114655 MongoDB CVE debrief

Who should care

Defenders responsible for libmongocrypt deployments, particularly those using key vault collections, should assess exposure and prioritize patching. Defenders should prioritize verifying their libmongocrypt versions and applying patches, as the vulnerability allows for potential manipulation of key management operations. Operators of systems using libmongocrypt, security teams, and vulnerability management teams should review their deployments and apply 7

Why it matters

The vulnerability in libmongocrypt allows for KMS request injection, potentially leading to unintended key management operations. Defenders should prioritize verifying their libmongocrypt versions and applying patches.

• Potential manipulation of key management operations
• Unintended key management operations may be performed
• Verification of libmongocrypt versions and patching is required
• Monitoring of key management operations for suspicious activity is necessary

Technical summary

The libmongocrypt library fails to validate or encode values from key vault documents, KMS provider configuration, and KMS responses, allowing for KMS request injection. A user with write access to the key vault collection can manipulate requests, potentially leading to unintended key management operations. This issue arises from the library's failure to validate or encode values from key vault documents, KMS provider configuration, and KMS responses before inserting them into request lines, headers, and signed request bodies.

Defensive priority

Defenders should prioritize verifying their libmongocrypt versions and applying patches, as the vulnerability allows for potential manipulation of key management operations.

Recommended defensive actions

• Verify libmongocrypt version and apply patches
• Review key vault collection access controls
• Monitor key management operations for suspicious activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to additional information. The libmongocrypt library fails to validate or encode values from key vault documents, KMS provider configuration, and KMS responses, allowing for KMS request injection. A user with write access to the key vault collection can manipulate requests, potentially leading to unintended key management operations. Defenders should verify their libmongocrypt versions and apply patches. No

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.