Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition as malicious server or MITM
-
DeliveryClient initiates SCRAM authentication
-
ExploitInject malformed server-final message
-
ExecutionTrigger out-of-bounds read in parser
-
ImpactCrash application using driver
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to supply the SCRAM server-final message before server-signature verification - meaning the attacker must operate the MongoDB server the client connects to, or sit as a network intermediary (MITM) within the authentication handshake. The client application must be using the MongoDB C Driver with SCRAM authentication. Limiting factors: the attacker cannot trigger this against a client talking to a legitimate, trusted server without MITM positioning (reflected as AT:P), the impact is confined to process termination (denial of service) with no data exposure, and no privileges or user interaction on the client are needed (PR:N/UI:N). |
| Impact | This is a medium-severity denial-of-service issue, not a high-priority emergency. The MongoDB-supplied CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N) scores 6.3 with availability-only impact (VA:L) and no confidentiality or integrity impact - consistent with the description, which explicitly states the out-of-bounds byte 'is not returned through the protocol,' so despite the 'Information Disclosure' tag there is NO actual data leak; the real impact is a crash of the application using the driver. The critical qualifier is AT:P (Attack Requirements: Present): exploitation requires the attacker to act as the MongoDB server endpoint or a network intermediary (MITM) able to inject the malformed server-final message before server-signature verification completes - this is NOT a flaw a random remote attacker can trigger against a client connecting to a trusted server. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or weaponization. Net assessment: a legitimate bug worth patching on a normal cycle, but the positioning precondition plus DoS-only impact keep real-world risk modest rather than urgent. |
| Exploit ScenarioDerived | An attacker who controls a malicious MongoDB server endpoint, or who can intercept traffic as a network intermediary during the SCRAM authentication handshake, sends a crafted malformed server-final message to a client built on the MongoDB C Driver. The driver reads one byte past a fixed-size buffer while parsing it, terminating the client application and causing denial of service. No public exploit was identified in the provided data, and the network vector is tempered by the requirement to be positioned in the authentication exchange (AT:P). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Denial of service in the MongoDB C Driver affects any application that uses the driver with SCRAM authentication, because a malformed SCRAM server-final message is parsed with a one-byte out-of-bounds read that can terminate the client process. The attacker must either operate the MongoDB server the client connects to or position themselves as a network intermediary inside the authentication handshake, since the bad message has to arrive before server-signature verification completes; unauthenticated remote delivery is possible under those conditions (CVSS:4.0 PR:N/UI:N, AT:P) but no client privileges or user interaction are required. Impact is limited to availability (VC:N/VI:N/VA:L) and the over-read byte is never returned through the protocol, so there is no data exposure; this is rated medium severity (CVSS 6.3 as published, 3.7 under our assessed CVSS:3.1/AV:N/AC:H vector), with no public exploit code and no confirmed active exploitation (CISA KEV) identified at time of analysis.
RemediationAI
No vendor-released patch was identified in the available intelligence, so the first action is to monitor https://jira.mongodb.org/browse/CDRIVER-6370 and apply the driver update as soon as MongoDB publishes a fixed release, including rebuilding and redeploying any application statically linked against the driver. As compensating controls, enforce encrypted and authenticated transport so an intermediary cannot inject the malicious server-final message: enable TLS with full certificate verification in the client connection string (tls=true with a trusted tlsCAFile and no tlsAllowInvalidCertificates or tlsAllowInvalidHostnames), which blocks the MITM path although it does not protect against a legitimate-but-malicious or compromised server. Where the topology allows it, connect only to servers whose identity is pinned or otherwise vetted, and restrict client egress so it can reach only the intended MongoDB endpoints. Operators who cannot immediately trust the server side can switch authentication away from SCRAM - for example MONGODB-X509 client certificates or PLAIN over TLS - accepting the trade-off that these require different server-side credential or certificate configuration and may not be available in every deployment. Finally, since the impact is process termination, run the client under a supervisor with automatic restart and alerting to limit the denial-of-service window, acknowledging that this reduces but does not eliminate the outage.
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 flaw is CWE-125 (out-of-bounds read) in the SCRAM authentication response parser of the MongoDB C Driver, the official client library used by C/C++ applications to talk to MongoDB. During SCRAM (Salted Challenge Response Mechanism) authentication the client consumes a server-final message containing the server signature; the parser handles this fixed-size buffer and, when the message is malformed, reads one byte past the end of that buffer. The affected component is tracked under the affected CPE cpe:2.3:a:mongodb:c_driver:*:*:*:*:*:*:*:* against the public vendor record https://jira.mongodb.org/browse/CDRIVER-6370, which is the authoritative advisory reference for this issue. Because the mis-sized read occurs before server-signature verification, an attacker who controls the responding server endpoint or who intercepts the handshake can supply the crafted message; the out-of-bounds byte is not propagated back to the caller or the protocol, so the practical effect is crash/termination of the hosting process rather than memory disclosure. The overlap with the 'Buffer Overflow' and 'Information Disclosure' tags in the source metadata should be read cautiously: the described primitive is an over-read of a single byte with no disclosed content, and the authoritative assessment classifies the outcome as availability-only.
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:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
AC:H maps the 4.0 AT:P positioning requirement (attacker must be the server or MITM in the handshake); PR:N/UI:N as none needed; impact is DoS only, so A:L and C:N/I:N.
Primary rating from Vendor (mongodb).
CVSS VectorVendor: mongodb
Lifecycle Timeline
1DescriptionCVE.org
An out-of-bounds read in SCRAM authentication response parsing in the MongoDB C Driver can read one byte beyond a fixed-size buffer when processing a malformed server-final message. A server or network intermediary able to provide this message before server-signature verification can cause the application using the driver to terminate. The extra byte is not returned through the protocol.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
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-95144
NVD
CVE.org
EPSS
Vulnrichment
VulDB
GitHub PoC
Exploit-DB