Threats / MongoDB / CVE-2025-14847
CVE-2025-14847
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
MongoDB and Server vulnerability
MongoDB Server improperly handles length parameters in Zlib compressed protocol headers, allowing unauthenticated clients to read uninitialized heap memory.
Verdict
Today item — known-exploited.
An unauthenticated attacker can exploit improper length parameter validation in MongoDB's Zlib compression handling to leak sensitive heap memory contents without authentication, potentially exposing credentials or other sensitive data.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-12-29).
Probability (EPSS)
EPSS 0.83007 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: MongoDB, MongoDB and MongoDB Server. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-130 CWE-130.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
WeaknessCWE-130 · CWE-130
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malformed Zlib compressed protocol header with inconsistent length parameters to trigger heap memory read operations.
Business
Sensitive data including credentials, encryption keys, or user information stored in heap memory becomes accessible to unauthenticated attackers.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I repeatedly send crafted requests to extract uninitialized heap memory and reconstruct sensitive information across multiple responses.
Business
Confidentiality of customer data and internal secrets is compromised, creating regulatory compliance violations and reputational damage.
3
Lateral reach — past segmentation narrative 3
Attacker
I use leaked memory contents to identify running software versions, internal structures, or authentication tokens for further exploitation.
Business
Attack surface expands as leaked information enables lateral movement and privilege escalation within the infrastructure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05