MongoBleed memory leak CVE-2025-14847 exploited as 87,000 MongoDB servers remain exposed

A vulnerability in MongoDB Server dubbed MongoBleed (CVE-2025-14847) is being exploited in the wild. It lets unauthenticated attackers read uninitialised heap memory from database servers. A working proof-of-concept appeared on 26 December 2025, scans soon showed more than 87,000 potentially vulnerable internet-facing servers, and CISA added the flaw to its Known Exploited Vulnerabilities catalog on 29 December.

What happened

MongoDB disclosed the issue on 19 December 2025 and released fixes for all supported branches. Elastic researcher Joe Desimone named the bug and published an exploit, and attacks followed quickly. MongoDB stresses that the flaw does not allow code execution. The risk is that leaked memory may contain credentials, session tokens, query data or other secrets that the server was handling.

Technical details

  • Root cause: the server mishandles length fields in zlib-compressed wire protocol messages, so it returns memory that was never initialised.
  • Preconditions: network access to the MongoDB port and zlib compression enabled, which it is by default. No authentication is needed.
  • Severity: MongoDB rates it CVSS 7.5. Some outlets cite a CVSS 4.0 score of 8.7.
  • Fixed versions: 8.2.3, 8.0.17, 7.0.28, 6.0.27, 5.0.32 and 4.4.30
  • No fix: end-of-life branches 4.2, 4.0 and 3.6 remain vulnerable.

MongoDB says there is no workaround short of upgrading. Atlas customers received the patch automatically.

Who is affected

Any self-managed MongoDB deployment on an affected branch that is reachable from untrusted networks is at risk. That includes development and staging databases exposed to the internet by mistake.

Recommendations

  • Upgrade to the fixed release for your branch immediately. Migrate any 4.2 or older deployments to a supported version.
  • Remove direct internet exposure of port 27017 and restrict access to application hosts and VPN ranges.
  • Review MongoDB server logs for bursts of malformed compressed messages from unknown IPs. Even patched servers may have been probed before the update.
  • Assume secrets that passed through exposed servers may have leaked, and rotate database users, application credentials and any keys held in memory.

Sources