Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach an endpoint that deserializes untrusted BSON/JSON
-
DeliverySubmit content with many unique BSON symbol values
-
ExploitDriver interns each symbol with no limit
-
ExecutionRetained data accumulates for process lifetime
-
ImpactHost memory exhausted, denial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource allocation limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the host application actually deserializes attacker-influenced BSON or JSON input using the MongoDB C driver, and that the supplied content carries BSON symbol (BsonSymbol) values - the specific value type whose interning is unbounded. The weakness is that deserialized symbols are interned and retained for the entire process lifetime with no cap, so attacker-supplied symbols accumulate across requests. Limiting factors: the application must expose a deserialization path to untrusted data (not inherent to merely having the driver installed), only availability is affected (no confidentiality or integrity impact), no MongoDB server component is affected, and the CVSS marks attack complexity as high (AC:H); the detailed reason for AC:H is not described in the available sources. Fixed in driver v3.13.0, where BsonSymbol values are no longer interned. |
| Impact | Signals point to a real but bounded availability risk rather than a top-tier emergency. The vendor (MongoDB CNA) CVSS 4.0 vector is AV:N/AC:H/AT:N/PR:N/UI:N with VA:H and VC:N/VI:N - i.e. a network-reachable, unauthenticated denial of service affecting availability only, scored 8.2. The AC:H metric indicates the attack is not entirely trivial/attacker-controlled, which tempers the otherwise high base score; per the supplied evidence the precise trigger difficulty is not elaborated, so AC:H should be read as severity, not as a described race or timing condition. The vuln.today decision label is 'this_week', consistent with a serious-but-not-drop-everything DoS. Exploitation status: no public exploit identified at time of analysis (the two references are a vendor release tag and a Jira ticket, neither a working exploit). No EPSS score was provided in the input, so exploitation probability cannot be quantified - this is missing data, not a low score. CVE is NOT listed in CISA KEV. Net: a genuine unauthenticated remote DoS in a widely used .NET library, worth prioritized patching to v3.13.0, but confidentiality and integrity are explicitly unaffected and no server component is impacted, so it is not a critical compromise-class issue. |
| Exploit ScenarioDerived | A .NET application uses the MongoDB C driver to deserialize BSON or JSON content that originates from an untrusted remote party. The attacker repeatedly submits content containing many distinct BSON symbol values; because each symbol is interned and retained for the lifetime of the process, memory grows without bound until the host application is exhausted and service is denied. No public exploit was identified, and the CVSS marks attack complexity as high (AC:H). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 22, 2026
Signals point to a real but bounded availability risk rather than a top-tier emergency: the MongoDB C
Driver's BSON library interns every BsonSymbol produced during deserialization and retains those symbols for the lifetime of the process with no cap, so an unauthenticated remote party able to get attacker-influenced BSON or JSON deserialized can drive unbounded memory growth and deny service to the host application (availability-only; assessed CVSS 3.1 AV:N/AC:H/PR:N/UI:N/C:N/I:N/A:H, CNA CVSS 4.0 score 8.2). Exposure is conditional - the application must actually deserialize untrusted content through the driver and that content must carry BSON symbol values; merely having the driver installed is not a trigger, and no MongoDB server component is affected. No public exploit code or confirmed active exploitation has been identified at time of analysis; version 3.13.0 removes symbol interning as the fix.
RemediationAI
Vendor-released patch: .NET Driver 3.13.0 - upgrade to 3.13.0 or later (https://github.com/mongodb/mongo-csharp-driver/releases/tag/v3.13.0), which per CSHARP-6162 (https://jira.mongodb.org/browse/CSHARP-6162) no longer interns BsonSymbol values and marks BsonSymbolTable obsolete. Code that relied on interned symbols should switch to BsonSymbol.Create or the implicit string conversion; equality still compares by name, but reference-identity comparisons will change, so audit any code that compared BsonSymbol instances by reference before deploying. Because the same release also carries behavioral fixes for CSHARP-6157, CSHARP-6166 and CSHARP-6168 (stricter rejection of malformed raw BSON, out-of-range binary subtypes and injected update operators), review those behavior changes too - writes that previously succeeded with malformed input will now throw. No patch-level workaround is documented by the vendor; short of upgrading, the only lever traceable to the described exposure is to stop feeding untrusted BSON or JSON into the driver's deserialization paths (or to strip/whitelist symbol-typed fields before deserialization), which may not be feasible for applications whose core function is relaying user-supplied documents and which will still leave the process-wide interning table growing.
Affected VersionsENISA
Affected Packages
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 weakness is CWE-770 (Allocation of Resources Without Limits or Throttling) applied to BSON deserialization. BSON defines a symbol value type, surfaced in the .NET driver as BsonSymbol; historically these were canonicalized through a process-wide BsonSymbolTable that interns each distinct symbol name and keeps it reachable forever. Because the table has no size bound and entries are never released, every unique attacker-supplied symbol survives for the lifetime of the process and accumulates across requests until host memory is exhausted - a slow, cumulative resource drain rather than a single-request crash. The CNA's CVSS 4.0 vector is network-reachable, unauthenticated (PR:N) and availability-high with no confidentiality or integrity impact, and the independent assessment marks attack complexity high (AC:H); the specific reason for that complexity rating is not described in the available sources, and the exact input path (raw BSON reader, JSON reader, or a driver-serialized type mapping to BsonSymbol) is likewise not detailed beyond 'deserialization handling of one BSON value type.' The 3.13.0 fix (CSHARP-6162) stops interning BsonSymbol values and marks BsonSymbolTable obsolete; BsonSymbol.Create or implicit string conversion replaces it, equality still compares by name, and only reference identity semantics change. That same release also closes several unrelated BSON hardening issues - CSHARP-6157 (raw BSON length-prefix mismatch enabling NoSQL command injection), CSHARP-6166 (out-of-range binary subtypes corrupting BSON output) and CSHARP-6168 (update-builder operator injection) - so the underlying library hardening is broader than this CVE alone.
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
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Network-reachable unauthenticated deserialization of untrusted content (AV:N/PR:N/UI:N) with availability-only memory-exhaustion impact (A:H, C:N/I:N); AC:H retained to match vendor's complexity assessment.
Primary rating from Vendor (mongodb).
CVSS VectorVendor: mongodb
Lifecycle Timeline
2DescriptionCVE.org
The MongoDB C
Driver's BSON library contains an uncontrolled resource consumption weakness in its deserialization handling of one BSON value type. An application that deserializes untrusted content with the library retains data derived from that content for the lifetime of the process, with no limit on how much accumulates. An unauthenticated remote party who can cause such content to be deserialized can drive unbounded memory growth, exhausting the host application's available memory and denying service. There is no impact to confidentiality or integrity, and no MongoDB server component is affected.
Executive ViewAI
CVE-2026-114644 affects the MongoDB C
Driver's BSON library, where unauthenticated attackers can cause memory exhaustion by deserializing malicious BSON/JSON containing symbols, leading to denial of service for applications using the driver. This is a high-severity availability risk that could disrupt critical business services if exploited. Leadership should prioritize patching to prevent potential outages and operational impact.
No vendor-released patch identified at time of analysis.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMo
The find prototype in scripting/engine_v8.h in MongoDB 2.4.0 through 2.4.4 allows remote authenticated users to cause a
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
Remote code execution in Chartbrew versions prior to 4.8.1 allows authenticated attackers with high privileges to execut
After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated user's
The default configuration for MongoDB before 2.3.2 does not validate objects, which allows remote authenticated users to
SimStudio below 0.5.74 has a missing authorization on MongoDB tool endpoints that allows attackers to execute arbitrary
MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are calle
MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of e
Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which ma
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. Rated critical severity (CVSS 9.8
Memory corruption in the MongoDB BI Connector ODBC Driver (fixed in v1.4.9) occurs when an oversized catalog, schema, or
EUVD-2026-108305
NVD
CVE.org
GitHub
Exploit-DB