CVE-2026-106430

Query and rename target confusion via embedded NUL truncation in MongoDB C++ Driver

Published Oct 8, 2026 CVSS 4.0 · 6 Medium EPSS < 1% KEV · Not listed
Description
The MongoDB C++ Driver discards content after an embedded NUL byte in certain field and collection names accepted by the collection API. This can cause the driver and the calling application to interpret the same name differently. An authenticated actor who can influence a name passed by an affected application can cause the application to read distinct values from an unintended field or rename an unintended collection. These operations use the application's existing database credentials.

Analysis

AI-generated

Technical impact

The MongoDB C++ Driver discards content after an embedded NUL byte in field and collection names supplied to the driver. This truncation creates a source‑output confusion vulnerability where the driver and the calling application interpret the same name differently. As a result, an authenticated user with the ability to influence a name can cause the application to read from an unintended field or rename an unintended collection, exposing confidential data or altering database objects. The flaw relies solely on the application’s existing database credentials and does not require higher privileges.

Affected Systems

MongoDB C++ Driver is the affected product. No specific affected versions are listed, so the issue applies to all releases that contain the described truncation behavior.

Risk and Exploitability

The CVSS score of 6.0 indicates medium severity. EPSS is not available and the vulnerability is not listed in CISA’s KEV catalog, suggesting no documented public exploitation at the time of the advisory. The likely attack vector is an authenticated actor who can specify collection or field names; by including an embedded NUL byte the driver truncates the name while the application uses the full string, leading to unintended data access or object renaming. The risk is bounded to accounts that possess write or administrative rights on the database.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the MongoDB C++ Driver to a version that addresses the NUL truncation issue when it becomes available.
  • Validate all collection and field names in the application to reject or strip embedded NUL bytes before passing them to the driver.
  • Enforce least‑privilege database credentials; restrict user rights so that only trusted accounts can rename collections or access sensitive fields.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Mongodb c\+\+ Driver
CPEs cpe:2.3:a:mongodb:c\+\+_driver:*:*:*:*:*:mongodb:*:*
Vendors & Products Mongodb c\+\+ Driver
Type Values Removed Values Added
First Time appeared Mongodb
Mongodb c++ Driver
Vendors & Products Mongodb
Mongodb c++ Driver
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 MongoDB C++ Driver discards content after an embedded NUL byte in certain field and collection names accepted by the collection API. This can cause the driver and the calling application to interpret the same name differently. An authenticated actor who can influence a name passed by an affected application can cause the application to read distinct values from an unintended field or rename an unintended collection. These operations use the application's existing database credentials.
Title Query and rename target confusion via embedded NUL truncation in MongoDB C++ Driver
Weaknesses CWE-436
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses

Sources

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