
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-4359 is a Denial of Service vulnerability in the MongoDB C driver caused by improper null byte handling when processing HTTP responses. A compromised third-party cloud server or a man-in-the-middle (MitM) attacker can send a malformed HTTP response that triggers a crash in applications using the affected driver. The vulnerability affects MongoDB C driver versions prior to 1.30.8 and versions 2.2.0 through 2.2.3. It was disclosed on March 17, 2026, and carries a CVSS v3.1 base score of 3.7 (Low) and a CVSS v4.0 base score of 2.0 (Low) (Red Hat Advisory, Red Hat Bugzilla).
The root cause is classified under CWE-158 (Improper Neutralization of Null Byte or NUL Character) and CWE-170 (Improper Null Termination), meaning the driver fails to correctly handle null bytes embedded in or improperly terminating HTTP response data. An attacker positioned as a MitM or controlling a third-party cloud server the application communicates with can craft a malformed HTTP response containing null byte sequences that the driver does not properly sanitize or terminate, leading to a crash. Exploitation requires high attack complexity, the presence of specific attack conditions (e.g., network positioning), and high privileges, significantly limiting the practical attack surface. The vulnerability is tracked upstream in the MongoDB JIRA as CDRIVER-6251 (MongoDB JIRA, Red Hat Bugzilla).
Successful exploitation results in a crash of applications using the vulnerable MongoDB C driver, causing a denial of service (service unavailability). The impact is limited to availability — there is no confidentiality or integrity impact, meaning data exposure or unauthorized modification is not a concern with this vulnerability. The affected scope is unchanged, meaning the crash is contained to the application using the driver and does not propagate to other system components (Red Hat Advisory, MongoDB JIRA).
There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time. The EPSS score is approximately 0.03%, reflecting a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires a high-complexity attack scenario — specifically, the attacker must either compromise a third-party cloud server the application trusts or achieve a MitM network position, both of which are significant barriers (Red Hat Advisory).
Users should upgrade the MongoDB C driver to version 1.30.8 or later (for the 1.x branch) or version 2.2.3 or later (for the 2.x branch), which contain the fix for this vulnerability. As a network-level mitigation, organizations should implement certificate pinning and enforce encrypted TLS connections to prevent MitM attacks against MongoDB driver communications. Monitoring applications for unexpected crashes or availability issues related to HTTP response handling can help detect exploitation attempts (MongoDB JIRA, Red Hat Advisory).
Coverage of this vulnerability has been limited to standard vulnerability tracking and advisory channels, including Red Hat Bugzilla, the ENISA European Vulnerability Database (EUVD-2026-12640), and German Linux security news outlet Pro-Linux.de, which published brief advisories on the denial of service issue. No notable researcher commentary or significant community discussion has been observed, consistent with the low severity and limited exploitability of the vulnerability.
Fix availability across major Linux distributions and their releases.
bookworm
mongo-c-driver: 1.23.1-1+deb12u3
sid
mongo-c-driver: 2.2.3-1
trixie
mongo-c-driver: 1.30.4-1+deb13u2
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."