Improper state management in MongoDB libmongocrypt can cause provider-specific data to be treated as an incompatible type when cleaning up a key document containing duplicate masterKey fields. An authenticated actor who can modify key vault documents, or a server that returns such a key document, can cause invalid memory access and invalid frees in the client process. This can terminate the application or corrupt process memory.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://jira.mongodb.org/browse/MONGOCRYPT-964 Vendor Advisory, Issue Tracking
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 3
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-27 20:17
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-27 20:17
- First seenCVSS 8.7NVD modified 2026-10-08 20:49
Affected (CPE criteria) 1
cpe:2.3:a:mongodb:libmongocrypt:*:*:*:*:*:*:*:*
References 1
- https://jira.mongodb.org/browse/MONGOCRYPT-964 Vendor Advisory, Issue Tracking