Skip to main content

MongoDB C# Driver CVE-2026-114646

| EUVDEUVD-2026-108310 MEDIUM
Improper Handling of Length Parameter Inconsistency (CWE-130)
2026-10-22 cna@mongodb.com
6.9
CVSS 4.0 · Vendor: mongodb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Supply crafted binary with mismatched BSON length prefix
  2. Delivery
    Application builds raw/lazy BSON document from it
  3. Exploit
    Driver writes buffer verbatim to wire
  4. Execution
    Injected/removed elements alter database command
  5. Impact
    Unauthorized data modification or out-of-scope disclosure

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Length parameter validation
Exploitation Conditions

Exploitation requires the target application to construct a raw BSON document or array (RawBsonDocument/LazyBsonDocument) from externally supplied binary data and then issue it as or within a database command, using a vulnerable driver version (2.0.0 up to but excluding 3.13.0). The specific trigger is a BSON length prefix that does not match the actual buffer, which the pre-fix driver copies to the wire verbatim; impact is bounded by the database privileges the application itself holds. The main limiting factor is this application coding pattern - apps that do not build BSON from attacker-influenced binary input are not exposed - rather than any network or authentication barrier (PR:N, UI:N). No EPSS/KEV data and no working public exploit were provided.

Impact

This is a medium-severity (CVSS 4.0 base 6.9) NoSQL/BSON command-injection flaw (CWE-130, length-parameter inconsistency) in the MongoDB C

Driver, confirmed and scored by the MongoDB CNA. The CVSS vector AV:N/AC:L/AT:N/PR:N/UI:N indicates a network-reachable issue requiring no privileges or user interaction, with limited confidentiality and integrity impact (VC:L/VI:L) and no availability impact. The 'unauthenticated' characterization is supported by PR:N and by the description, which notes the attacker needs no database credentials of their own - but the real limiter is a code-path precondition, not an access-control one: the victim application must itself construct a raw or lazy BSON document from externally supplied binary data and send it on the wire. It is therefore not blanket remote-unauthenticated exploitation of a default service; it depends on how the application uses the driver. No EPSS score and no KEV status were supplied, and there is no CISA KEV listing in the input, so there is no signal of active exploitation; the only references are the vendor release notes and the CSHARP-6157 JIRA ticket, neither of which is a working exploit. The vuln.today decision label is 'this_month' (not act_now/emergency), consistent with a real-but-not-urgent priority: patch in a normal maintenance cycle. One conflict to verify: the input Tags label this 'Authentication Bypass', but the vendor release notes explicitly describe CSHARP-6157 as 'NoSQL command injection' - the tag appears mislabeled and the vulnerability is an injection/data-validation flaw, not an authentication bypass.

Exploit ScenarioDerived

An application uses the MongoDB C

Driver to build a RawBsonDocument or LazyBsonDocument directly from binary data that an unauthenticated external party can influence (for example an uploaded or forwarded binary blob), then issues a database command built from it. Because the driver copies the buffer to the wire without checking that the declared BSON length prefix matches the actual data, the attacker crafts a mismatched length prefix so that extra command elements are appended or existing ones dropped, altering the command the application sends. No public working exploit was identified at time of analysis; only the vendor advisory and JIRA ticket are referenced.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 22, 2026

A BSON length-parameter inconsistency (CWE-130) in the MongoDB C

Driver prior to 3.13.0 lets unauthenticated remote attackers inject or remove elements in database commands issued by applications that build raw or lazy BSON documents from externally supplied binary data. Because the pre-fix driver copies the attacker's mismatched length prefix onto the wire verbatim instead of validating it against the actual buffer size, the server parses the excess or truncated elements as part of the command, enabling unauthorized modification and out-of-scope disclosure of stored data bounded by the application's own database privileges. Exploitation depends on that specific application coding pattern rather than on any authentication or user-interaction barrier (PR:N, UI:N); no public exploit code or KEV listing was provided, and the fix is the vendor's 3.13.0 GA release.

RemediationAI

Upgrade the MongoDB C

Driver NuGet package to 3.13.0 or later, the vendor-released fix that makes writing a raw BSON document or array throw ArgumentException when its declared length is inconsistent with the buffer, with bytes past the declared length ignored (CSHARP-6157, release notes at https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.13.0). Because 3.13.0 also introduces documented behavior changes - BsonSymbol values are no longer interned and BsonSymbolTable is obsolete (CSHARP-6162), and BsonBinaryData, the JSON reader and the binary writer now reject binary subtypes outside 0 to 255 (CSHARP-6166) - regression-test code that relies on symbol reference identity, on out-of-range subtype values, or on loosely formed raw BSON before rolling out, since previously tolerated inputs will now raise exceptions. Until the upgrade is deployed, reduce exposure by eliminating the dangerous pattern: do not construct RawBsonDocument or LazyBsonDocument from request-supplied bytes; parse untrusted input into validated typed models with explicit size and field-count limits and re-serialize server-side, accepting the added CPU and allocation cost for large payloads. As a secondary containment measure, run the application's MongoDB user with the minimum privileges its commands require so that any injected command elements can only touch the collections and operations the application legitimately needs, understanding this bounds but does not prevent the injection. No vendor patch version earlier than 3.13.0 is identified in the available data.

Affected VersionsENISA

C# Driver 2.0.0 <3.13.0

Affected Packages

euvd c_driver fix: 3.13.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

BSON is the binary serialization format MongoDB uses for documents and commands; each document begins with a little-endian int32 length prefix declaring the total byte size. The MongoDB C

Driver's RawBsonDocument and LazyBsonDocument types are designed to hold pre-serialized BSON and forward it without full materialization, and before 3.13.0 the write path performed no check that the declared length matched the supplied buffer, so a length prefix longer or shorter than the actual data was transmitted unchanged. That is the classic CWE-130 length-parameter inconsistency class: the server trusts the embedded length to determine where the document ends, so bytes beyond the declared end (or a re-framed boundary) can be parsed as additional command elements, or genuine elements can fall outside the parsed region. The result is NoSQL command injection at the driver layer (CSHARP-6157) rather than at the query-language layer. The same 3.13.0 release hardened several related parsing paths: out-of-range binary subtypes are now rejected (CSHARP-6166), symbol interning is no longer unbounded (CSHARP-6162), and update-builder list rewriting and schema/LINQ name handling were made stricter. The relevant technology stack is .NET applications using the official MongoDB.Driver package; the flaw is in client-side serialization, so exposure is determined entirely by whether the application feeds attacker-controlled binary into the raw/lazy BSON constructors and then sends it as part of a command.

Know when MongoDB gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mongodb) PRIMARY 6.9 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 6.5 MEDIUM

Attacker supplies binary data over the network with no credentials or interaction (AV:N/AC:L/PR:N/UI:N); impact is limited and bounded by the app's DB privileges (C:L/I:L/A:N), scope unchanged per vendor treatment.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mongodb).

CVSS VectorVendor: mongodb

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
Patch available
Oct 22, 2026 - 20:18 EUVD

DescriptionCVE.org

A data-validation flaw exists in the BSON handling and binary serialization path of the MongoDB C

Driver. When an application constructs a raw or lazy BSON document object from externally supplied binary data, the driver does not verify that the size quantity declared inside that data matches the amount of data actually provided, and it copies the data onto the wire unchanged. An unauthenticated party who can supply binary content to such an application can thereby cause additional elements to be inserted into, or existing elements to be removed from, the database command the application issues, without needing any database credentials of their own. This can result in unauthorized modification of stored data and disclosure of data outside the intended scope of the application's request, bounded by the database privileges the application itself holds.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Prevalence
Medium
official MongoDB .NET/C# driver, popular library but limited to .NET MongoDB apps
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

34
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0
CVE-2013-1892 MEDIUM POC
6.0 Oct 01

MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMo

CVE-2013-3969 MEDIUM POC
6.5 Oct 01

The find prototype in scripting/engine_v8.h in MongoDB 2.4.0 through 2.4.4 allows remote authenticated users to cause a

CVE-2018-13863 HIGH POC
7.5 Jul 10

The MongoDB bson JavaScript module (also known as js-bson) versions 0.5.0 to 1.0.x before 1.0.5 is vulnerable to a Regul

CVE-2026-25887 HIGH POC
7.2 Mar 06

Remote code execution in Chartbrew versions prior to 4.8.1 allows authenticated attackers with high privileges to execut

CVE-2019-2386 HIGH POC
7.1 Aug 06

After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated user's

CVE-2012-6619 MEDIUM POC
6.4 Mar 06

The default configuration for MongoDB before 2.3.2 does not validate objects, which allows remote authenticated users to

CVE-2026-3431 CRITICAL
9.8 Mar 02

SimStudio below 0.5.74 has a missing authorization on MongoDB tool endpoints that allows attackers to execute arbitrary

CVE-2024-8654 CRITICAL
9.8 Sep 10

MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are calle

CVE-2024-6376 CRITICAL
9.8 Jul 01

MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of e

CVE-2024-1351 CRITICAL
9.8 Mar 07

Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which ma

CVE-2020-7610 CRITICAL
9.8 Mar 30

All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. Rated critical severity (CVSS 9.8

CVE-2026-19001 CRITICAL
9.5 Aug 12

Memory corruption in the MongoDB BI Connector ODBC Driver (fixed in v1.4.9) occurs when an oversized catalog, schema, or

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy