CVE-2026-106434

Unrecognized payload acceptance in explicit decryption in MongoDB libmongocrypt

Published Oct 8, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
The explicit decryption component of MongoDB libmongocrypt can return an unrecognized encrypted payload unchanged instead of returning a decryption error. An actor who can modify stored encrypted fields, such as a database writer, server, or network intermediary, can cause an affected application to process the supplied bytes as decrypted plaintext.

Analysis

AI-generated

Technical impact

The library provides explicit decryption that, when encountering an unrecognized encrypted payload, returns the raw bytes unchanged instead of signaling a decryption failure. This flaw means an attacker who can alter stored encrypted data can cause the application to treat the corrupted blob as a legitimate plaintext value, potentially leading to incorrect application behavior or data corruption. The weakness arises from improper error handling during decryption (CWE-354).

Affected Systems

This vulnerability affects the MongoDB libmongocrypt component. No specific version range is listed, so all releases of MongoDB libmongocrypt that have not yet absorbed the fix are potentially impacted.

Risk and Exploitability

The CVSS score of 5.3 indicates a medium risk. The EPSS score is not available, so the public exploitation probability is unclear, and the vulnerability is not listed in the CISA KEV catalog. Attackers would need the ability to modify encrypted fields, such as a database writer, an unauthorized server, or a network intermediary. The likely attack vector is through compromised write access or tampering with data in transit; if an attacker succeeds, the affected application could process the tampered payload as plaintext, leading to data integrity issues.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade libmongocrypt to the latest version that includes the patch for MONGOCRYPT-966.
  • Ensure the application checks and handles decryption errors appropriately, so that any failure from libmongocrypt does not lead to the use of unverified data.
  • Restrict write permissions to encrypted fields to trusted services and consider implementing integrity auditing to detect unauthorized modifications.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
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': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description The explicit decryption component of MongoDB libmongocrypt can return an unrecognized encrypted payload unchanged instead of returning a decryption error. An actor who can modify stored encrypted fields, such as a database writer, server, or network intermediary, can cause an affected application to process the supplied bytes as decrypted plaintext.
Title Unrecognized payload acceptance in explicit decryption in MongoDB libmongocrypt
Weaknesses CWE-354
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses
  • CWE-354

    Improper Validation of Integrity Check Value

Sources

Status
PUBLISHED
Assigner
mongodb
Published
Updated
Oct 8, 2026, 7:30 PM
Reserved
Oct 6, 2026, 4:40 PM
Status
Awaiting Analysis
Published
Oct 8, 2026, 7:16 PM
Modified
Oct 8, 2026, 8:49 PM