CVE-2026-81523

Cross-tenant database retargeting via dot/NUL injection in namespace strings in libmongocrypt

Published Aug 27, 2026 CVSS 4.0 · 2 Low EPSS < 1% KEV · Not listed
Description
A missing input-validation issue in MongoDB libmongocrypt's automatic-encryption context setup allows a caller-supplied database identifier to be accepted without sanitization. The resulting impact is limited to incorrect schema selection, which may lead to limited disclosure or modification of information handled by the application.

Analysis

AI-generated

Technical impact

A missing input‑validation flaw in MongoDB’s libmongocrypt allows a caller to supply a database identifier containing dot or NUL characters without sanitization. The flaw occurs during automatic‑encryption context setup and results in an incorrect schema being selected. This can lead to limited disclosure or modification of the information handled by the application. The weakness is a classic CWE-74 "Improper Neutralization of Special Elements used in a Command (Command Injection)" scenario.

Affected Systems

MongoDB’s libmongocrypt component is affected. The issue has been addressed in the 1.20.3 release, though explicit version ranges impacted are not listed in the available data.

Risk and Exploitability

The vulnerability carries a CVSS score of 2, indicating low severity. No EPSS value is available, and the vulnerability is not listed in the CISA KEV catalog. Exploitability appears to require the ability to supply a database identifier to libmongocrypt, implying an attacker must already be able to execute code in the application’s context or supply malicious configuration. The impact is limited to incorrect schema use rather than full system compromise.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade libmongocrypt to version 1.20.3 or later to apply the vendor fix.
  • Validate any database identifiers supplied to the application to ensure they contain only permitted characters and reject dot or NUL characters before passing them to libmongocrypt.
  • Review automatic encryption context configuration to confirm that only approved schema names are used, and remove any logic that allows arbitrary database names to be forwarded to the cryptographic library.

Generated by OpenCVE AI on August 28, 2026 at 08:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

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
Description A missing input-validation issue in MongoDB libmongocrypt's automatic-encryption context setup allows a caller-supplied database identifier to be accepted without sanitization. The resulting impact is limited to incorrect schema selection, which may lead to limited disclosure or modification of information handled by the application.
Title Cross-tenant database retargeting via dot/NUL injection in namespace strings in libmongocrypt
Weaknesses CWE-74
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses
  • CWE-74

    Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Sources

Status
PUBLISHED
Assigner
mongodb
Published
Updated
Aug 28, 2026, 3:51 PM
Reserved
Aug 26, 2026, 10:13 PM
Status
Analyzed
Published
Aug 27, 2026, 8:18 PM
Modified
Sep 17, 2026, 1:59 PM