Libmongocrypt
Monthly
Memory corruption in MongoDB libmongocrypt lets an authenticated actor who can modify key vault documents - or a malicious or compromised MongoDB server - crash or corrupt the memory of any client application that has Client-Side Field Level Encryption (CSFLE) or Queryable Encryption enabled. The trigger is a crafted key document containing duplicate masterKey fields, which causes provider-specific KMS data to be mis-typed during key-document cleanup, producing invalid memory access and invalid frees (CWE-843 type confusion). Scored 8.7 under CVSS 4.0, while our own assessment is more conservative at CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H, placing the confirmed impact at client-side crash and memory corruption rather than proven remote code execution; no public exploit code identified at time of analysis, and exploitation requires that encryption be in use plus key-vault write privileges (PR:L) or a hostile server.
Denial of service in MongoDB libmongocrypt occurs when KMS endpoint parsing triggers an integer underflow, causing an allocation failure that terminates the application process. This can be triggered by an authenticated user with write access to the key vault collection modifying a key document, or when an application passes a KMS endpoint containing a colon after its path or query during key creation. No public exploit code has been identified at time of analysis, and the vulnerability does not allow code execution, data disclosure, or data tampering-only a crash.
Process-terminating denial of service in libmongocrypt's decryption path allows a low-privileged attacker to crash applications using MongoDB Client-Side Field Level Encryption (CSFLE). Tracked as MONGOCRYPT-971, the vulnerability is triggered when an unexpected-size encrypted value reaches the decryption routine, firing a reachable assertion (CWE-617) that abruptly terminates the host process rather than returning a handled error. An attacker who can store crafted encrypted values in a shared MongoDB collection, or influence the encrypted data an application receives, can repeatably crash the targeted application.
MongoDB libmongocrypt's explicit decryption component can return unrecognized encrypted payloads unchanged instead of raising a decryption error, causing affected applications to process attacker-supplied bytes as plaintext. This is a moderate integrity flaw (CVSS 4.0 score 5.3) that requires the application to use explicit client-side field level encryption and the attacker to already hold write access to stored encrypted fields or an in-path position to tamper with ciphertext, such as a database writer, a malicious or compromised MongoDB server, or a network intermediary. No public exploit code or CISA KEV listing was identified at time of analysis, and applications that do not use explicit decryption are unaffected.
Unauthorized write access to a MongoDB key vault collection allows an attacker to inject maliciously crafted key metadata into libmongocrypt, causing a legitimate authorized application client to issue arbitrary Google Cloud KMS API calls authenticated under the victim client's GCP identity. All versions of libmongocrypt are listed as affected via CPE wildcard (`cpe:2.3:a:mongodb:libmongocrypt:*`), with impact limited to deployments using MongoDB Client-Side Field Level Encryption (CSFLE) or Queryable Encryption configured with a Google Cloud KMS key provider. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Input injection in MongoDB libmongocrypt's automatic-encryption context setup permits caller-supplied database and collection name arguments containing '.' or NUL bytes to pass without sanitization, causing incorrect schema selection during Client-Side Field Level Encryption (CSFLE) operations. Affected callers - those with local access and low privileges - may obtain limited unauthorized disclosure or modification of data processed under the wrong encryption schema. No public exploit code exists and this vulnerability is not in CISA KEV; the CVSS 4.0 score of 2.0 reflects the constrained real-world impact.
A specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS server’s certificate. Rated medium severity (CVSS 6.8), this vulnerability is no authentication required. No vendor patch available.
Memory corruption in MongoDB libmongocrypt lets an authenticated actor who can modify key vault documents - or a malicious or compromised MongoDB server - crash or corrupt the memory of any client application that has Client-Side Field Level Encryption (CSFLE) or Queryable Encryption enabled. The trigger is a crafted key document containing duplicate masterKey fields, which causes provider-specific KMS data to be mis-typed during key-document cleanup, producing invalid memory access and invalid frees (CWE-843 type confusion). Scored 8.7 under CVSS 4.0, while our own assessment is more conservative at CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H, placing the confirmed impact at client-side crash and memory corruption rather than proven remote code execution; no public exploit code identified at time of analysis, and exploitation requires that encryption be in use plus key-vault write privileges (PR:L) or a hostile server.
Denial of service in MongoDB libmongocrypt occurs when KMS endpoint parsing triggers an integer underflow, causing an allocation failure that terminates the application process. This can be triggered by an authenticated user with write access to the key vault collection modifying a key document, or when an application passes a KMS endpoint containing a colon after its path or query during key creation. No public exploit code has been identified at time of analysis, and the vulnerability does not allow code execution, data disclosure, or data tampering-only a crash.
Process-terminating denial of service in libmongocrypt's decryption path allows a low-privileged attacker to crash applications using MongoDB Client-Side Field Level Encryption (CSFLE). Tracked as MONGOCRYPT-971, the vulnerability is triggered when an unexpected-size encrypted value reaches the decryption routine, firing a reachable assertion (CWE-617) that abruptly terminates the host process rather than returning a handled error. An attacker who can store crafted encrypted values in a shared MongoDB collection, or influence the encrypted data an application receives, can repeatably crash the targeted application.
MongoDB libmongocrypt's explicit decryption component can return unrecognized encrypted payloads unchanged instead of raising a decryption error, causing affected applications to process attacker-supplied bytes as plaintext. This is a moderate integrity flaw (CVSS 4.0 score 5.3) that requires the application to use explicit client-side field level encryption and the attacker to already hold write access to stored encrypted fields or an in-path position to tamper with ciphertext, such as a database writer, a malicious or compromised MongoDB server, or a network intermediary. No public exploit code or CISA KEV listing was identified at time of analysis, and applications that do not use explicit decryption are unaffected.
Unauthorized write access to a MongoDB key vault collection allows an attacker to inject maliciously crafted key metadata into libmongocrypt, causing a legitimate authorized application client to issue arbitrary Google Cloud KMS API calls authenticated under the victim client's GCP identity. All versions of libmongocrypt are listed as affected via CPE wildcard (`cpe:2.3:a:mongodb:libmongocrypt:*`), with impact limited to deployments using MongoDB Client-Side Field Level Encryption (CSFLE) or Queryable Encryption configured with a Google Cloud KMS key provider. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.
Input injection in MongoDB libmongocrypt's automatic-encryption context setup permits caller-supplied database and collection name arguments containing '.' or NUL bytes to pass without sanitization, causing incorrect schema selection during Client-Side Field Level Encryption (CSFLE) operations. Affected callers - those with local access and low privileges - may obtain limited unauthorized disclosure or modification of data processed under the wrong encryption schema. No public exploit code exists and this vulnerability is not in CISA KEV; the CVSS 4.0 score of 2.0 reflects the constrained real-world impact.
A specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS server’s certificate. Rated medium severity (CVSS 6.8), this vulnerability is no authentication required. No vendor patch available.