CVE-2025-15614

LOWPre-NVD 3.33.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 3.3 from GitHub Security Advisory published 2026-09-05. The CNA's CVSS baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
3.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ugrep before 7.6.0 contains a heap buffer over-read vulnerability in the LZW decompressor when processing crafted .Z archive files. Attackers can supply malformed .Z files that cause the decompressor to read one byte past the allocated heap buffer, potentially crashing the process.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity33% × 45%
The EG Score, 3.3 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 5, 2026

Last Modified

September 24, 2026

References (6)

Vendor Advisories for CVE-2025-15614(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ugrep3.11.2+dfsg-1 ... 7.8.4+dfsg-1 (38 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ugrep7.4.2+dfsg-1 ... 7.8.4+dfsg-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ugrep7.4.2+dfsg-1, 7.5.0+dfsg-1
  • every version up to 7.6.0+dfsg-1: fixed in 7.6.0+dfsg-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 63 are merged into the row they repeat.

  1. 2026-10-11 20:53 UTCEG score recompute
  2. 2026-10-11 19:03 UTCEG score recompute
  3. 2026-10-11 15:43 UTCEG score recompute
  4. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-09 22:59 UTCEG score recompute
  6. 2026-10-09 22:59 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  7. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-06 13:06 UTCEG score recompute
  12. 2026-10-06 13:06 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-03 14:16 UTCEG score recompute
  17. 2026-10-03 14:16 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-30 15:23 UTCEG score recompute
  20. 2026-09-30 15:23 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  21. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-27 14:14 UTCEG score recompute
  24. 2026-09-27 14:14 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  25. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.1% · 1st percentile
Show 36 more
  1. 2026-09-24 14:55 UTCEG score recompute
  2. 2026-09-24 14:55 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  3. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-09-23 17:23 UTCEG score recompute
  5. 2026-09-23 17:23 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  6. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-09-22 11:33 UTCEG score recompute
  9. 2026-09-22 11:33 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  10. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-09-19 12:45 UTCEG score recompute
  12. 2026-09-19 12:45 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  13. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-09-16 13:56 UTCEG score recompute
  16. 2026-09-16 13:56 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  17. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-13 15:06 UTCEG score recompute
  21. 2026-09-13 15:06 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  22. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-09-10 16:17 UTCEG score recompute
  26. 2026-09-10 16:17 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  27. 2026-09-10 15:27 UTCEG score recompute
  28. 2026-09-10 15:27 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  29. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-09-08 11:13 UTCEG score recompute
  32. 2026-09-08 11:13 UTCGHSA enrichmentGHSA-85v4-hj64-h8x4 · GitHub CVSS 3.3
  33. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  34. 2026-09-05 12:22 UTCEG score recompute
  35. 2026-09-05 11:44 UTCEG score recomputeFirst assessed: 3.3 LOW
  36. 2026-09-05 11:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-15614?
CVE-2025-15614 is a low-severity vulnerability; its CVE record was published on September 5, 2026. ugrep before 7.6.0 contains a heap buffer over-read vulnerability in the LZW decompressor when processing crafted .Z archive files. Attackers can supply malformed .Z files that cause the decompressor to read one byte past the allocated heap buffer, potentially crashing the process.
When was CVE-2025-15614 made public?
CVE-2025-15614 was made public on October 15, 2025: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 5, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2025-15614 actively exploited?
CVE-2025-15614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-15614?
CVE-2025-15614 has a CVSS base score of 3.3 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2025-15614?
A fix for CVE-2025-15614 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-15614 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-15614

Explore →

Is Your Infrastructure Affected by CVE-2025-15614?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs