dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 19 Jan 2026.
MongoDBDatabase / datastore

CVE-2025-14847

HIGH · 7.5 CVSS v3.1 Published 2025-12-19
Fix available
A fix is available. Upgrade to 4.4.30 / 5.0.32 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in MongoDB Server's Zlib compressed protocol header handling allows unauthenticated clients to read uninitialized heap memory due to mismatched length fields in the compression headers, enabling potential information disclosure.

MitigationUpgrade MongoDB Server to the fixed version appropriate for your major version branch: 7.0.28+, 8.0.17+, 8.2.3+, 6.0.27+, 5.0.32+, 4.4.30+, or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MongoDBDatabase / datastore
Affected:>= 3.6.0, < 4.4.30>= 5.0.0, < 5.0.32>= 6.0.0, < 6.0.27>= 7.0.0, < 7.0.28>= 8.0.0, < 8.0.17>= 8.2.0, < 8.2.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MongoDB Server version
    Run 'db.version()' in the MongoDB shell or 'mongod --version' / 'mongos --version' from the command line
    Affected if The version falls within any of these ranges: >= 3.6.0 and < 4.4.30, >= 5.0.0 and < 5.0.32, >= 6.0.0 and < 6.0.27, >= 7.0.0 and < 7.0.28, >= 8.0.0 and < 8.0.17, or >= 8.2.0 and < 8.2.3
  2. Verify if wire protocol compression is enabled
    Check the MongoDB configuration file (mongod.conf or mongos.conf) for 'net.compression.enabled' settings, or run 'db.adminCommand({getCmdLineOpts: 1}).parsed.net.compression' in the shell
    Affected if Wire protocol compression is explicitly enabled (any compressor setting other than 'disabled' or not set at all)

You are affected if your MongoDB version is in the vulnerable range AND wire protocol compression is enabled, allowing unauthenticated remote attackers to potentially read uninitialized heap memory via the Zlib compression handling in the wire protocol.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.4.30 / 5.0.32 / 6.0.27 or later
Fixed in 4.4.305.0.326.0.27
Vendor patch jira.mongodb.org →
Interim mitigation

Upgrade MongoDB Server to the fixed version appropriate for your major version branch: 7.0.28+, 8.0.17+, 8.2.3+, 6.0.27+, 5.0.32+, 4.4.30+, or later.

Recommended fix High confidence

Upgrade to 4.4.30 / 5.0.32 / 6.0.27 / 7.0.28 (or latest patch in your respective version branch)

  1. Identify the currently installed MongoDB Server version using: db.version() or mongod --version
  2. Determine which version branch you are running (3.6.x, 4.0.x, 4.2.x, 4.4.x, 5.0.x, 6.0.x, or 7.0.x)
  3. For MongoDB 4.4.x: Upgrade to version 4.4.30 or later
  4. For MongoDB 5.0.x: Upgrade to version 5.0.32 or later
  5. For MongoDB 6.0.x: Upgrade to version 6.0.27 or later
  6. For MongoDB 7.0.x: Upgrade to version 7.0.28 or later
  7. For MongoDB 8.0.x: Upgrade to version 8.0.17 or later (if applicable)
  8. For MongoDB 8.2.x: Upgrade to version 8.2.3 or later (if applicable)
Caveat Review MongoDB release notes for any backward compatibility changes between your current version and target version; test application drivers for compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MongoDB Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14847 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data