How severe is CVE-2025-14847?

No CVSS score has been assigned to CVE-2025-14847 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-14847?

Affected package information for CVE-2025-14847 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-14847?

Upgrade the affected component to the fixed release for CVE-2025-14847, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect CVE-2025-14847 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2025-14847 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-14847 actively exploited in the wild?

Yes. There are 8 known exploit references for CVE-2025-14847, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2025-14847?

CVE-2025-14847 has an EPSS (Exploit Prediction Scoring System) score of 83.2%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2025-14847 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-14847 (MongoDB and MongoDB Server Improper Handling of Length Parameter Inconsistency Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-12-29. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-01-19. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-14847?

CVE-2025-14847 is classified as CWE-130 (CWE-130). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2025-14847?

2 Metasploit modules reference CVE-2025-14847, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2025-14847 published, and has it been updated?

CVE-2025-14847 was published on December 19, 2025 and was last updated on October 21, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2025-14847 — mongo

CVE-2025-14847 is a CWE-130 vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-12-29) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.

Zlib compressed protocol header length confusion may allow memory read

Also known asBIT-mongodb-2025-14847

Published

Dec 19, 2025

Updated

Oct 21, 2026

Affected

1 product

Patched

See advisory

Exploits

8 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2025-12-29. Federal agencies were required to remediate by 2026-01-19.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2025-14847.

EPSS Exploitation Probability

via FIRST.org ↗

83.2%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

Affected Products

1 product · 6 configurations

Application

mongodbmongodb

≥ 8.2.0 && < 8.2.3

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Black1hp/mongobleed-scanner

MongoDB CVE-2025-14847 Heap Memory Leak Scanner | OP_COMPRESSED zlib Vul

⭐ 35🍴 5Jul 2026

cybertechajju/CVE-2025-14847_Expolit

a critical memory disclosure vulnerability in MongoDB's zlib compression

⭐ 34🍴 3Aug 2026

ProbiusOfficial/CVE-2025-14847

poc for CVE-2025-14847

⭐ 26🍴 6Sep 2026

onewinner/CVE-2025-14847

MongoDB 内存泄露漏洞 (CVE-2025-14847) 检测工具

⭐ 15🍴 2Sep 2026

Security-Phoenix-demo/mongobleed-exploit-CVE-2025-14847

Exploit lab, docker and code scanner for mongobleed Vulnerability CVE-20

⭐ 13🍴 2Jun 2026

codeb0ssx/CVE-2025-14847-PoC

Academic proof-of-concept demonstrating CVE-2025-14847 for authorized se

⭐ 4🍴 0May 2026

joshuavanderpoll/CVE-2025-14847

CVE-2025-14847 (MongoBleed)

⭐ 4🍴 0Aug 2026

franksec42/mongobleed-exploit-CVE-2025-14847

Explot, Lab, Scanner - external and docker container, for SMongobleed-CV

⭐ 3🍴 1Feb 2026

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for CVE-2025-14847, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-14847 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works