CVE-2025-14847
Zlib compressed protocol header length confusion may allow memory read
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Description
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 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.
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Black1hp/mongobleed-scanner
MongoDB CVE-2025-14847 Heap Memory Leak Scanner | OP_COMPRESSED zlib Vul
cybertechajju/CVE-2025-14847_Expolit
a critical memory disclosure vulnerability in MongoDB's zlib compression
ProbiusOfficial/CVE-2025-14847
poc for CVE-2025-14847
onewinner/CVE-2025-14847
MongoDB 内存泄露漏洞 (CVE-2025-14847) 检测工具
Security-Phoenix-demo/mongobleed-exploit-CVE-2025-14847
Exploit lab, docker and code scanner for mongobleed Vulnerability CVE-20
chinaxploiter/CVE-2025-14847-PoC
Academic proof-of-concept demonstrating CVE-2025-14847 for authorized se
franksec42/mongobleed-exploit-CVE-2025-14847
Explot, Lab, Scanner - external and docker container, for SMongobleed-CV
joshuavanderpoll/CVE-2025-14847
CVE-2025-14847 (MongoBleed)
Detection & mitigation playbook
VulnerabilityDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for the affected component. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of the affected component has shipped for CVE-2025-14847 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-14847 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-14847. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-14847 in your dependencies?
O3 detects CVE-2025-14847 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.