CVE-2026-106433

Heap corruption via duplicate masterKey fields in MongoDB libmongocrypt

Published Oct 8, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An improper state management bug in MongoDB libmongocrypt allows provider-specific data to be processed as an incompatible type during the cleanup of a key document that contains duplicate masterKey fields. The flaw can lead to invalid memory access and invalid frees in the client process. When triggered, it can terminate the application or corrupt process memory, potentially compromising the confidentiality, integrity, or availability of the affected system. This weakness is cataloged as CWE-843.

Affected Systems

MongoDB’s libmongocrypt library is affected. The vulnerability can be exploited by any authenticated actor who can modify key‑vault documents or by a server that returns a key document with duplicate masterKey fields. The specific version ranges impacted were not disclosed in the available data.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity. No EPSS score is currently available, so the exploitation probability is not quantified. The vulnerability is not listed in the CISA KEV catalog, implying no known active exploitation at the time of assessment. Based on the description, the likely attack vector requires either an authenticated user with write access to key‑vault documents or a compromised server capable of returning malformed key documents. A successful exploit will cause a crash or memory corruption in a client process that interacts with libmongocrypt.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update to the latest version of MongoDB libmongocrypt where the duplicate masterKey handling bug is fixed
  • Validate that all key‑vault documents conform to the expected schema and do not contain duplicate masterKey fields
  • Implement or enforce strict input validation on any external source that can supply key‑vault documents to prevent malformed data from reaching the client

Generated by OpenCVE AI on October 8, 2026 at 20:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:mongodb:libmongocrypt:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Mongodb
Mongodb libmongocrypt
Vendors & Products Mongodb
Mongodb libmongocrypt
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

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

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-843

    Access of Resource Using Incompatible Type ('Type Confusion')

Sources

Status
PUBLISHED
Assigner
mongodb
Published
Updated
Oct 8, 2026, 7:30 PM
Reserved
Oct 6, 2026, 4:40 PM
Status
Analyzed
Published
Oct 8, 2026, 7:16 PM
Modified
Oct 27, 2026, 8:17 PM