Actively exploited vulnerability

MongoDB and MongoDB Server: memory corruption flaw under attack

CVE-2025-14847 · MongoDB and MongoDB Server Improper Handling of Length Parameter Inconsistency Vulnerability

Business software8.7 high

What is affected

MongoDB and MongoDB Server is mostly run by companies, schools and public bodies, not on home computers. You are unlikely to have it yourself, but organisations that hold your data may. Breaches that start with flaws like this one are how personal data ends up leaked.

MongoDB Server contains an improper handling of length parameter inconsistency vulnerability in Zlib compressed protocol headers. This vulnerability may allow a read of uninitialized heap memory by an unauthenticated client.

CISA's description

What an attacker can do

This is a memory corruption flaw. It lets an attacker corrupt the program's memory by feeding it specially crafted content: a web page, a file or a network message. The result ranges from a crash to the attacker running their own code.

How it is reached
Over the internet or network
Access the attacker needs
No account needed
Does the victim have to do something?
No, works without the victim doing anything

What to do

  1. At home: nothing to install. Keep your own devices updated and use a different password for every service, so that a breach at one organisation does not open your other accounts.
  2. If you administer MongoDB and MongoDB Server at work: apply the vendor's fix or mitigation now and review logs for signs of compromise, because the flaw was being exploited before it was listed.
  3. If the product is past its support date and no fix exists, take it off the internet or retire it.

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Action required by CISA for US federal agencies

Vendor advisories and fixes

How urgent is it

CISA added this vulnerability to its Known Exploited Vulnerabilities catalogue on December 29, 2025, which means there is reliable evidence of attacks in the wild. US federal agencies must fix it by January 19, 2026, a deadline that has already passed. That deadline does not bind anyone else, but it shows how seriously the agency rates it.

The EPSS model estimates a 83% probability that this flaw will be exploited somewhere in the next 30 days. That is higher than 99.7% of all scored vulnerabilities.

Its CVSS severity score is 8.7 out of 10 (high), as recorded in the US National Vulnerability Database.

Technical 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.

NIST National Vulnerability Database
5,442 members already hereReading, writing, commenting and voting. 0 verified · 167 joined this year