No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://jira.mongodb.org/browse/MONGOCRYPT-964 |
|
Thu, 08 Oct 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mongodb
Mongodb libmongocrypt |
|
| Vendors & Products |
Mongodb
Mongodb libmongocrypt |
Thu, 08 Oct 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 08 Oct 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Heap corruption via duplicate masterKey fields in MongoDB libmongocrypt | |
| Weaknesses | CWE-843 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: mongodb
Published:
Updated: 2026-10-08T19:30:26.703Z
Reserved: 2026-10-06T16:40:35.016Z
Link: CVE-2026-106433
Updated: 2026-10-08T19:30:22.387Z
Status : Awaiting Analysis
Published: 2026-10-08T19:16:59.233
Modified: 2026-10-08T20:49:23.240
Link: CVE-2026-106433
No data.
OpenCVE Enrichment
Updated: 2026-10-08T20:30:18Z