Cyber Resilience

CVE-2026-4359

Mongodb C Driver ≤ 1.30.8

Published
17 March 2026
Modified
02 April 2026
Patch / advisory
CVSS Score v4 2.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0019 8th percentile
Risk Priority 15 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-4359 is a low-severity Improper Neutralization of Null Byte or NUL Character (CWE-158) vulnerability in Mongodb C Driver. Its CVSS base score is 2.0 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A compromised third party cloud server or man-in-the-middle attacker could send a malformed HTTP response and cause a crash in applications using the MongoDB C driver.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-6231Same product: Mongodb C Driver
CVE-2026-6691Same product: Mongodb C Driver
CVE-2023-0437Same product: Mongodb C Driver
CVE-2024-10921Same vendor: Mongodb
CVE-2025-12119Same product: Mongodb C Driver
CVE-2025-66263Shared CWE-158
CVE-2026-43861Shared CWE-158
CVE-2025-47812Shared CWE-158
CVE-2026-43859Shared CWE-158
CVE-2026-47778Shared CWE-158

Affected Assets

mongodb
c driver
≤ 1.30.8 · 2.2.0 — 2.2.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.10

Mitigating Controls (NIST 800-53 r5) AI

Input validation directly requires neutralizing or rejecting malformed characters such as NUL before they reach downstream components.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and validation to prevent null-byte flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect null-byte flaws but does not itself implement the neutralization.

prevents

Secure development lifecycle mandates input validation and sanitization that directly prevents null-byte injection.

prevents

Application security requirements include explicit rules for neutralizing dangerous characters such as NUL.

prevents

Secure architecture principles reduce the likelihood of unsafe data flows but do not prescribe character neutralization.

prevents

Secure coding standards explicitly require proper neutralization of null bytes and other metacharacters.

References