87,000+ MongoDB Instances Vulnerable to MongoBleed Flaw Exposed Online – PoC Exploit Released
A critical vulnerability identified in MongoDB Server allows unauthenticated remote attackers to extract sensitive data from database memory. This vulnerability, designated as CVE-2025-14847 and referred to as "MongoBleed," has been assigned a CVSS score…
A critical vulnerability identified in MongoDB Server allows unauthenticated remote attackers to extract sensitive data from database memory. This vulnerability, designated as CVE-2025-14847 and referred to as "MongoBleed," has been assigned a CVSS score of 7.5. It was disclosed on December 19, 2025.
The MongoBleed vulnerability stems from an issue in the zlib message decompression implementation of MongoDB Server, leading to uninitialized memory disclosure. When a specially crafted packet is decompressed, a logic error can expose uninitialized heap memory. This memory may contain residual data from previous operations, including credentials and authentication tokens.
Exploitation of this vulnerability does not require authentication, allowing remote users with network access to the database port to trigger the flaw. Since zlib compression is enabled by default in standard MongoDB configurations, the potential attack surface is extensive.
According to Censys, over 87,000 MongoDB instances may be vulnerable and exposed to the public internet. The affected versions include:
A critical vulnerability identified in MongoDB Server allows unauthenticated remote attackers to extract sensitive data from database memory.
MongoDB 8.2: 8.2.0 – 8.2.2 MongoDB 8.0: 8.0.0 – 8.0.16 MongoDB 7.0: 7.0.0 – 7.0.27 MongoDB 6.0: 6.0.0 – 6.0.26 MongoDB 5.0: 5.0.0 – 5.0.31 MongoDB 4.4: 4.4.0 – 4.4.29 Legacy: All versions of 4.2, 4.0, and 3.6.
MongoDB has released patches to address this vulnerability. Administrators are advised to upgrade to the following versions or higher:
8.2.3, 8.0.17, 7.0.28, 6.0.27, 5.0.32, and 4.4.30
For organizations unable to apply patches immediately, disabling zlib compression can mitigate risk. This can be achieved by adjusting the networkMessageCompressors or net.compression.compressors settings to exclude zlib. Additionally, restricting network access to trusted IP addresses is recommended to prevent unauthorized access.
Based on reporting by Cyber Security News.
