Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-0755 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Mongodb Mongodb. Its CVSS base score is 8.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-0755 is a buffer overflow vulnerability in the bson_append functions of the MongoDB C driver library (libbson). It occurs when operations produce a BSON document exceeding the maximum allowable size of INT32_MAX, triggering a segmentation fault and potential application crash. The issue affects libbson versions prior to 1.27.5, MongoDB Server v8.0 versions prior to 8.0.1, and MongoDB Server v7.0 versions prior to 7.0.16. The vulnerability is classified under CWE-122 (Heap-based Buffer Overflow) with a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
A local attacker can exploit this vulnerability with low complexity and no privileges or user interaction required. By crafting operations that force the BSON document to exceed INT32_MAX, the attacker triggers the buffer overflow, resulting in a segmentation fault that crashes the affected application. The high impact ratings across confidentiality, integrity, and availability indicate potential for severe disruption, though the primary effect described is denial of service via crash.
Mitigation involves upgrading to patched versions: libbson 1.27.5 or later, MongoDB Server 8.0.1 or later, and MongoDB Server 7.0.16 or later. Official advisories, including MongoDB Jira tickets CDRIVER-5601 and SERVER-94461, detail the fixes, while Debian LTS announcements from May 2025 address backported patches for affected distributions.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6467
Vulnerability Data
The various bson_append functions in the MongoDB C driver library may be susceptible to buffer overflow when performing operations that could result in a final BSON document which exceeds the maximum allowable size (INT32_MAX), resulting in a segmentation fault and…
more
possible application crash. This issue affected libbson versions prior to 1.27.5, MongoDB Server v8.0 versions prior to 8.0.1 and MongoDB Server v7.0 versions prior to 7.0.16
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.
Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.
Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.
Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.
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.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
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.
Security testing in development and acceptance can detect heap overflows before release.
Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.
Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.
Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.
Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.
Change management ensures controlled deployment of fixes for discovered heap-overflow vulnerabilities.