vciy

CVE-2025-14847

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Zlib compressed protocol header length confusion may allow memory read

CVE-2025-148474 of 4 sources documented this
85

rank 85 = 40 + 22 + 9 + 6 + 8

rank@v1 · act now

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.83218 · CISA KEV listed  ·  without this subject the record ranks 45

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 8.7, from the CNA  ·  without this subject the record ranks 63

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-12-30  ·  without this subject the record ranks 76

How much of the world it touches

NVD CPE configurations

6 products in the CPE ranges  ·  without this subject the record ranks 79

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 77

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.54Mover the next 30 days, if this record is yours
Movement+$895,000on 2026-01-20, the last material move, 7 months before this reading
Basisassumeda published average, not your estate

$2.54M = $4.99M incident cost x 0.6121449559255632 exposure x 0.83218 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.83218EPSSKEV · LISTED
Severity8.7 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationin the wild · KEVreceipt
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 81 days at 0.83, as of 2026-09-04. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running MongoDB Server? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexity · no attack requirementsreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v4.0 · the CNA's vectorreceipt
Weakness classCWE-130 Improper Handling of Length Parameter Inconsistencyreceipt
Published consequencesCWE-130: Confidentiality, Integrity: Read Memory, Modify Memory, Varies by Context[email protected]
Ransomware campaign useUnknown to CISAreceipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in8.2.3; 8.0.17; 7.0.28; 6.0.27; 5.0.32; 4.4.30receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
CISA remediation statusoverdue since 2026-01-19receipt
CISA required actionApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.receipt
Published to CISA KEV10 daysderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Exploited in the wild · CISA KEV listed, 2025-12-29.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 36 public repositories2025-07-30receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2025-12-29receipt
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA8.7 HIGHreceipt
Exploit probability0.83218 · top 0.34% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymongodbreceipt
Recorded changes62 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMongoDB Inc. MongoDB Serverreceipt
Published rangesmongodb >= 3.6.0 < 4.4.30; mongodb >= 5.0.0 < 5.0.32; mongodb >= 6.0.0 < 6.0.27; mongodb >= 7.0.0 < 7.0.28receipt
Show all 6 published ranges
mongodb >= 3.6.0 < 4.4.30
mongodb >= 5.0.0 < 5.0.32
mongodb >= 6.0.0 < 6.0.27
mongodb >= 7.0.0 < 7.0.28
mongodb >= 8.0.0 < 8.0.17
mongodb >= 8.2.0 < 8.2.3
Fixed in8.2.3; 8.0.17; 7.0.28; 6.0.27; 5.0.32; 4.4.30receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

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

NVD's analysis a second authority

weakness
CWE-130
affected versions
mongodb >= 3.6.0 < 4.4.30; mongodb >= 5.0.0 < 5.0.32; mongodb >= 6.0.0 < 6.0.27; and 3 more, listed in full below
also scored by
[email protected] 8.7 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · [email protected] 7.5…

check it yourself jira.mongodb.org receipt

Dated events

2025-12-29Added to CISA KEV2025-12-30EPSS moved 0.00 to 0.582026-01-19CISA remediation due2026-06-15EPSS moved 0.63 to 0.83

Movement the material steps

19 Dec 20250.00031
30 Dec 20250.58251 · crossed 0.10 and 0.50
31 Dec 20250.77171
4 Jan 20260.65772
18 Jan 20260.2264 · crossed 0.50
20 Jan 20260.51951 · crossed 0.50
1 Feb 20260.62277
20 Mar 20260.74115
17 May 20260.61457
15 Jun 20260.83007 · scoring model v2026.06.15
16 Aug 20260.83218

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 48 observations
19 Dec 20250.00031
25 Dec 20250.00041
30 Dec 20250.58251
31 Dec 20250.77171
1 Jan 20260.68682
4 Jan 20260.65772
6 Jan 20260.68325
9 Jan 20260.69622
13 Jan 20260.67158
14 Jan 20260.57247
18 Jan 20260.2264
20 Jan 20260.51951
30 Jan 20260.58194
1 Feb 20260.62277
4 Feb 20260.58194
9 Feb 20260.60346
11 Feb 20260.60898
12 Feb 20260.59068
13 Feb 20260.57732
18 Feb 20260.65681
20 Feb 20260.6824
22 Feb 20260.68706
25 Feb 20260.64807
1 Mar 20260.68406
2 Mar 20260.71516
4 Mar 20260.68224
6 Mar 20260.68852
10 Mar 20260.71202
20 Mar 20260.74115
21 Mar 20260.71202
23 Mar 20260.74627
2 Apr 20260.75002
9 Apr 20260.77511
20 Apr 20260.76661
21 Apr 20260.74047
30 Apr 20260.74091
4 May 20260.767
11 May 20260.74804
13 May 20260.73532
15 May 20260.68941
17 May 20260.61457
22 May 20260.5888
26 May 20260.55832
3 Jun 20260.62808
5 Jun 20260.56927
8 Jun 20260.62808
15 Jun 20260.83007
16 Aug 20260.83218

48 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.83218Public PoC2025-07-30Published2025-12-19CISA KEV2025-12-29Index as of2026-09-04

Listed by CISA 10 days after it published, exploit probability more than doubled between 2026-01-18 and 2026-01-20 (0.2264 → 0.51951) and the record had been public for 8 months when this index was last written.

No material movement in 19 days as of the last ingest this index recorded.

Public PoC 2025-07-30 receipt · Published 2025-12-19 receipt · CISA KEV 2025-12-29 receipt · Index as of 2026-09-04 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2025-14847.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.