A flaw in MongoDB nicknamed MongoBleed lets attackers read data straight out of a database server's memory, without logging in first. It was disclosed on 28 December 2025, and attackers were already using it before the fix arrived. About 87,000 MongoDB servers are reachable from the public internet.

What is going on

The bug is tracked as CVE-2025-14847 and rated 8.7 on the severity scale of 10. It sits in the way MongoDB handles zlib compression, a common method for shrinking data before it travels over the network.

An attacker who can reach the server sends a crafted request and receives pieces of the server's working memory in reply. Think of asking a clerk for one page from a notebook and getting whatever pages happened to be next to it. Those pages can contain database passwords, API and cloud keys, session tokens and personal data.

No username or password is needed. Because the flaw was already exploited in the wild, CISA ordered US federal agencies to patch it.

Diagram showing how a MongoBleed request leaks server memory and how patching stops it
The crafted compressed request returns extra memory; the fixed build returns only the requested data.

Who is affected

Self-hosted MongoDB from version 3.6 through 8.2.x is affected, unless it already runs one of the fixed builds. MongoDB Atlas, the managed cloud version, was patched automatically by the vendor.

In practice this touches sites and apps that store data in their own MongoDB server: web shops, membership sites, mobile app back ends and analytics tools. If you are not sure what your site uses, your developer or hosting provider can tell you in a minute.

What to do now

  1. Ask your developer or host whether your site uses MongoDB, and which version.
  2. Upgrade to a fixed build: 8.2.3, 8.0.17, 7.0.28, 6.0.27, 5.0.32 or 4.4.30.
  3. Take MongoDB off the public internet, so only your own application servers can reach it.
  4. If the server was reachable from the internet, rotate the secrets it held: database passwords, API keys, cloud keys and session tokens.
  5. On MongoDB Atlas, confirm with your provider that the automatic patch has been applied.

How to check your own site

Our free Website Security Check looks at outdated CMS versions, known-vulnerable plugins, missing security headers, weak TLS and email-authentication gaps. It does not reach inside your database, so if you want to see which services are exposed to the internet and match them against known CVEs, run a full scan on a site whose ownership you have verified.

Source: BleepingComputer, December 2025.