Skip to main content

MongoDB C Driver EUVDEUVD-2026-70515

| CVE-2026-84963 MEDIUM
Incorrect Conversion between Numeric Types (CWE-681)
2026-09-03 mongodb
6.3
CVSS 4.0 · Vendor: mongodb
View

Attack ChainAIDerived

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

  1. Access
    Identify API endpoint passing JSON to MongoDB C Driver
  2. Delivery
    Craft payload with oversized numeric text field
  3. Exploit
    Submit request to target application
  4. Execution
    Driver silently truncates or drops field and reports success
  5. Persist
    Application persists corrupted/incomplete record
  6. Impact
    Exploit logical inconsistency in downstream processing

Vulnerability Assessment

Weakness
CWE
Exploitation Conditions

The target application must use the MongoDB C Driver's JSON-to-BSON parsing component to process input that originates, at least partially, from an external source. The attacker must control at least one numeric text field in that input and supply a value with an unusually large text representation that exceeds the BSON numeric type's valid range. No authentication is required based on PR:N in the CVSS 4.0 vector, but the attacker must have network reachability to an application-layer endpoint that passes their input through the affected driver code path. Exploitation is bounded by AT:P - a specific oversized input is required - and by the limited integrity impact (VI:L): only field truncation or silent omission is possible, not arbitrary value injection or overwrite. Applications that independently range-validate or schema-enforce numeric fields before driver ingestion are not exploitable via this path.

Impact

The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N) scores 6.3 (Medium). AT:P (Attack Requirements: Present) acknowledges that exploitation requires supplying an unusually large numeric text value, but this is a trivially reproducible condition for any attacker who controls input; it does not meaningfully raise the bar beyond a basic crafted payload. VI:L (Low integrity impact) accurately reflects the narrow scope - field-level truncation or omission rather than arbitrary data injection or system compromise. VC:N confirms there is no confidentiality exposure. No EPSS score, KEV listing, or public POC is provided, indicating no observed in-the-wild exploitation. Real-world risk escalates significantly in applications where numeric fields govern security-relevant decisions (financial thresholds, permission levels, rate limits, safety bounds), where silent truncation can produce logical inconsistencies that downstream logic exploits without triggering any observable error state. The missing exact affected and patched version numbers from the JIRA reference (CDRIVER-6407) make precise exposure assessment difficult for defenders.

Exploit ScenarioDerived

An attacker with access to an API endpoint that accepts JSON input and stores parsed results via the MongoDB C Driver submits a payload containing a numeric field whose text value exceeds the BSON target type's representable range - for example, an integer string far beyond 64-bit bounds. The driver silently truncates or drops the field and returns success; the application stores the corrupted record and proceeds normally. If the affected field governs a business logic decision such as a credit balance, permission flag, or rate-limit counter, the attacker may exploit the mismatch between the submitted and stored value to bypass controls or corrupt account state.

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

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

Alert me

AnalysisAIv1 – Sep 03, 2026

Silent data corruption in MongoDB C Driver's BSON JSON parsing component allows unauthenticated network attackers to cause applications to silently store truncated or dropped numeric fields. CWE-681 (incorrect conversion between numeric types) triggers when an oversized text-encoded numeric value is parsed: the driver returns a success result while the resulting BSON silently shortens or omits the field entirely. Applications depending on this library for accurate numeric representation - without independent input validation - may persist corrupt data without any indication of failure, creating exploitable logical inconsistencies. No public exploit code or active exploitation has been identified at time of analysis.

RemediationAI

Monitor the MongoDB JIRA ticket CDRIVER-6407 (https://jira.mongodb.org/browse/CDRIVER-6407) and the official MongoDB C Driver GitHub releases page for a patched version; no specific fix version is confirmed in available data, so citing a version number here would be speculative. As an interim compensating control, applications should independently validate numeric field values in incoming JSON against known-good ranges and maximum sizes before passing them to the C Driver for parsing - this adds defense-in-depth but requires per-field range knowledge and ongoing maintenance as schemas evolve. Restricting which callers can supply JSON to the affected processing path (e.g., requiring authentication, IP allowlisting, or schema-level type constraints at an API gateway) reduces attacker surface but does not eliminate the root defect. Applications processing numeric fields in security-critical contexts (financial, access control, safety) should consider temporarily treating oversized numeric values as parse errors in their own validation layer until the upstream driver fix is available.

Affected VersionsENISA

C Driver 1.10.0 <1.30.9
C Driver 2.0.0 <2.5.2

Affected Packages

euvd c_driver fix: 1.30.9, 2.5.2

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

The MongoDB C Driver provides the official C-language client for MongoDB, including a BSON (Binary JSON) encoding/decoding library used to serialize JSON input into the wire and storage format MongoDB requires. Based on CWE-681 (Incorrect Conversion Between Numeric Types), the JSON-to-BSON parser performs a type conversion when mapping a text-encoded numeric field to a fixed-width BSON numeric type. When the text representation's magnitude exceeds the target type's range, the conversion silently overflows, truncates, or omits the value rather than returning a parse error. Because the function reports success, callers have no programmatic signal that the stored value diverges from the submitted input. The affected product is identified by CPE cpe:2.3:a:mongodb:c_driver:*:*:*:*:*:*:*:* with a wildcard version range, indicating the issue spans an undisclosed span of releases.

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.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 5.3 MEDIUM

Network-reachable, no authentication required, no confidentiality or availability impact; only low integrity loss from silent field truncation or omission.

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

Primary rating from Vendor (mongodb).

CVSS VectorVendor: mongodb

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
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
Sep 03, 2026 - 17:01 EUVD

DescriptionCVE.org

An incorrect numeric conversion in the JSON parsing component of the MongoDB C Driver's BSON library may cause an unusually large text value to be silently shortened, or the corresponding field to be omitted, while the parsing operation still reports success and returns no error. An unauthenticated party who can supply the input processed by an application that uses this component may cause that application to hold data that does not match what was submitted, which may result in unintended alteration of data.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Medium
widely used C client library across MongoDB-backed applications
Data Quality
7 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.2%
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
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
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

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed

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