CVE-2025-14847
Mongodb 3.6.0 – 4.4.30
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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:XSummary
CVE-2025-14847 is a high-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Mongodb Mongodb. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
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-14847 involves mismatched length fields in Zlib compressed protocol headers within MongoDB Server, potentially allowing an unauthenticated client to read uninitialized heap memory. This vulnerability affects multiple versions across several MongoDB Server branches: all v7.0 prior to 7.0.28, v8.0 prior to 8.0.17, v8.2 prior to 8.2.3, v6.0 prior to 6.0.27, v5.0 prior to 5.0.32, v4.4 prior to 4.4.30, v4.2 versions greater than or equal to 4.2.0, v4.0 versions greater than or equal to 4.0.0, and v3.6 versions greater than or equal to 3.6.0. It is associated with CWE-130 (Improper Handling of Length Parameter Inconsistency) and carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
An unauthenticated remote attacker can exploit this issue over the network with low attack complexity and no user interaction required. Successful exploitation enables disclosure of uninitialized heap memory contents, providing high-impact confidentiality without affecting integrity or availability.
Advisories indicate mitigation through upgrading to patched releases where available, such as MongoDB Server v7.0.28, v8.0.17, v8.2.3, v6.0.27, v5.0.32, and v4.4.30. References include MongoDB's JIRA ticket SERVER-115508, an OSS-Security mailing list announcement, and third-party resources offering detection and mitigation scripts for heap memory exposure in this context.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-204529
Vulnerability Data
Mismatched length fields in Zlib compressed protocol headers may allow a read of uninitialized heap memory by an unauthenticated client. This issue affects all MongoDB Server v7.0 prior to 7.0.28 versions, MongoDB Server v8.0 versions prior to 8.0.17, MongoDB Server…
more
v8.2 versions prior to 8.2.3, MongoDB Server v6.0 versions prior to 6.0.27, MongoDB Server v5.0 versions prior to 5.0.32, MongoDB Server v4.4 versions prior to 4.4.30, MongoDB Server v4.2 versions greater than or equal to 4.2.0, MongoDB Server v4.0 versions greater than or equal to 4.0.0, and MongoDB Server v3.6 versions greater than or equal to 3.6.0.
- CWE(s)
- KEV Date Added
- 29 December 2025
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.5V4.2.1V4.2.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover length-parameter inconsistencies through targeted parsing tests.
Input validation enforces correct length-to-data consistency checks on parsed messages before processing.
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 SDLC practices directly enforce length validation and input sanitization during coding and review.
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 can detect length-inconsistency vulnerabilities before deployment.
Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.
Application security requirements include explicit rules for handling message lengths and data structures.
Secure architecture principles require robust parsing and bounds checking to prevent length-related flaws.
Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.