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.
References
| Link | Resource |
|---|---|
| https://jira.mongodb.org/browse/MONGOCRYPT-964 | Vendor Advisory Issue Tracking |
Configurations
History
27 Oct 2026, 20:17
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:mongodb:libmongocrypt:*:*:*:*:*:*:*:* | |
| First Time |
Mongodb libmongocrypt
Mongodb |
|
| References | () https://jira.mongodb.org/browse/MONGOCRYPT-964 - Vendor Advisory, Issue Tracking |
08 Oct 2026, 19:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-08 19:16
Updated : 2026-10-27 20:17
NVD link : CVE-2026-106433
Mitre link : CVE-2026-106433
CVE.ORG link : CVE-2026-106433
JSON object : View
Products Affected
mongodb
- libmongocrypt
CWE
CWE-843
Access of Resource Using Incompatible Type ('Type Confusion')
