Skip to content

CVE-2025-14847 BIT-mongodb-2025-14847

Zlib compressed protocol header length confusion may allow memory read

High Known exploited
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
83.22%
Chance of exploitation in the next 30 days. Higher than 99.68% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Dec 29, 2025
Weakness
CWE-130 Improper Handling of Length Parameter Inconsistency
Fix
None yet
No fixed version published
Exploited in the wild. MongoDB and MongoDB Server Improper Handling of Length Parameter Inconsistency Vulnerability (MongoDB MongoDB and MongoDB Server). Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Due for U.S. federal agencies by Jan 19, 2026.

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.

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
High
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-130: Improper Handling of Length Parameter Inconsistency

The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.

How to prevent it
  • Implementation: When processing structured incoming data containing a size field followed by raw data, ensure that you identify and resolve any inconsistencies between the size field and the actual size of the data.
  • Implementation: Do not let the user control the size of the buffer.
  • Implementation: Validate that the length of the user-supplied data is consistent with the buffer size.

References

Timeline

  1. Published
  2. Added to CISA's Known Exploited Vulnerabilities catalog
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-w26r-rmm8-9c29
Django has an Improper Handling of Length Parameter Inconsistency
Medium Same weakness, CWE-130
GHSA-hppc-g8h3-xhp3
rust-openssl: Unchecked callback length in PSK/cookie trampolines leaks adjacent memory to peer
Medium Same weakness, CWE-130
GHSA-q2ww-5357-x388
Rack has Content-Length mismatch in Rack::Files error responses
Medium Same weakness, CWE-130
GHSA-r836-hh6v-rg5g
Django vulnerable to denial-of-service attack
High Same weakness, CWE-130
GHSA-795c-9xpc-xw6g
Django vulnerable to a denial-of-service attack
High Same weakness, CWE-130
GHSA-qg2p-9jwr-mmqf
Django vulnerable to Denial of Service
High Same weakness, CWE-130
GHSA-f6f8-9mx6-9mx2
Django vulnerable to Denial of Service
High Same weakness, CWE-130
GHSA-5v95-j4rr-6f3c
rdiffweb's unlimited username field length can lead to DoS
High Same weakness, CWE-130
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor