{"id":"CVE-2026-106433","published":"2026-10-08T19:16:59.233","lastModified":"2026-10-08T20:49:23.240","description":"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.","cvssScore":8.8,"cvssSeverity":"HIGH","cvssVector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","cwes":["CWE-843"],"vendors":[],"products":[],"references":[{"url":"https://jira.mongodb.org/browse/MONGOCRYPT-964","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":{"summary":"The flaw involves improper state management in MongoDB's libmongocrypt, allowing an authenticated actor to cause memory corruption and application termination. This matters because it can lead to service disruption and potential data corruption.","exploitability":"Exploitation requires an authenticated actor who can modify key vault documents. The attack is moderately complex and depends on the ability to inject specific payload data.","blast_radius":"If exploited, this can terminate the application or corrupt process memory, impacting the availability and integrity of the MongoDB service.","remediation":"Upgrade to the latest version of MongoDB that addresses this vulnerability, specifically version 4.4.16 or later.","detection":"No reliable host or network indicator is derivable from the published description.","tags":["memory-corruption","auth-required","service-disruption"],"model":"qwen2.5:7b-instruct","analyzedAt":"2026-10-09T08:43:57.139Z"}}