CVE-2026-8997

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

vifm is vulnerable to a heap buffer overflow during the history merge process when saving the state file (vifminfo.json). This flaw occurs because the application lacks a runtime check on the length of history entries in release builds, potentially allowing a crafted long path or command in the history to cause memory corruption or application crashes. Releases from 0.12.1 to 0.14.3 (including) are considered vulnerable. This issue was fixed in commit 23063c7

CVSS v3
4.8
EG Score
4.8(medium)
EG Risk
22(Track)
EG Risk 22/100SSVC: Track

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
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

May 26, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 26, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 23063c741f15 (vifm/vifm)

Fix landed in vifm/vifm commit 23063c741f15 — awaiting tagged release

https://github.com/vifm/vifm/commit/23063c741f15a85621fd232dfc3ac5b779f6910d
generic

Vulnerability in vifm software | CERT Polska

https://cert.pl/en/posts/2026/05/CVE-2026-8997

Vendor Advisories for CVE-2026-8997(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
vifm0.10.1-4 ... 0.14.4-1 (10 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
vifm0.12-1 ... 0.14.4-1 (9 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
vifm0.14-3, 0.14.3-1, 0.14.3-2, 0.14.3-3, 0.14.4-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
vifm0.14-3, 0.14.3-1, 0.14.3-20.14.3-3—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 180 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-13 16:48 UTCEPSS rescore
  4. 2026-09-12 15:02 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 09:38 UTCEPSS rescore
  7. 2026-09-11 03:23 UTCOSV refresh
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-06 13:48 UTCEPSS rescore
  11. 2026-09-05 15:31 UTCEPSS rescore
  12. 2026-09-04 05:07 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 04:40 UTCEPSS rescore
  15. 2026-08-30 19:18 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:42 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:47 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 14:18 UTCEPSS rescore
  22. 2026-08-23 16:23 UTCEG score recompute
  23. 2026-08-23 16:23 UTCGHSA enrichment
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 21:30 UTCEG score recompute
  2. 2026-08-21 21:30 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 18:20 UTCEG score recompute
  5. 2026-08-20 18:20 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-17 09:35 UTCEG score recompute
  11. 2026-08-17 09:35 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 03:08 UTCEG score recompute
  15. 2026-08-16 03:08 UTCGHSA enrichment
  16. 2026-08-16 02:15 UTCEPSS rescore
  17. 2026-08-15 01:31 UTCEPSS rescore
  18. 2026-08-14 23:49 UTCGHSA enrichment
  19. 2026-08-14 01:44 UTCEG score recompute
  20. 2026-08-14 01:44 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 20:32 UTCEG score recompute
  23. 2026-08-12 20:32 UTCGHSA enrichment
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 22:27 UTCEG score recompute
  26. 2026-08-11 22:27 UTCGHSA enrichment
  27. 2026-08-11 13:43 UTCEPSS rescore
  28. 2026-08-11 00:23 UTCEG score recompute
  29. 2026-08-11 00:23 UTCGHSA enrichment
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-09 22:01 UTCEG score recompute
  32. 2026-08-09 22:01 UTCGHSA enrichment
  33. 2026-08-09 13:47 UTCEPSS rescore
  34. 2026-08-08 23:56 UTCEG score recompute
  35. 2026-08-08 23:56 UTCGHSA enrichment
  36. 2026-08-08 16:37 UTCEPSS rescore
  37. 2026-08-07 17:14 UTCEG score recompute
  38. 2026-08-07 17:14 UTCGHSA enrichment
  39. 2026-08-07 16:30 UTCEPSS rescore
  40. 2026-08-06 19:09 UTCEG score recompute
  41. 2026-08-06 19:09 UTCGHSA enrichment
  42. 2026-08-06 13:47 UTCEPSS rescore
  43. 2026-08-05 21:04 UTCEG score recompute
  44. 2026-08-05 21:04 UTCGHSA enrichment
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 15:10 UTCEPSS rescore
  48. 2026-08-04 10:39 UTCEPSS rescore
  49. 2026-08-03 16:42 UTCEG score recompute
  50. 2026-08-03 16:42 UTCGHSA enrichment
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 14:44 UTCEG score recompute
  53. 2026-08-02 14:44 UTCGHSA enrichment
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-01 16:39 UTCEG score recompute
  56. 2026-08-01 16:39 UTCGHSA enrichment
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-30 16:28 UTCEPSS rescore
  59. 2026-07-30 01:30 UTCEPSS rescore
  60. 2026-07-29 16:54 UTCEG score recompute
  61. 2026-07-29 16:54 UTCGHSA enrichment
  62. 2026-07-28 15:37 UTCEPSS rescore
  63. 2026-07-27 14:14 UTCEPSS rescore
  64. 2026-07-26 14:54 UTCEPSS rescore
  65. 2026-07-26 07:52 UTCEG score recompute
  66. 2026-07-26 07:52 UTCGHSA enrichment
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-24 14:18 UTCEPSS rescore
  69. 2026-07-23 16:11 UTCNVD updateCVSS v3 → 4.8
  70. 2026-07-23 14:18 UTCEPSS rescore
  71. 2026-07-23 03:23 UTCEG score recompute
  72. 2026-07-22 14:08 UTCEPSS rescore
  73. 2026-07-21 15:25 UTCEPSS rescore
  74. 2026-07-21 15:25 UTCEPSS rescore
  75. 2026-07-20 17:08 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-8997?
CVE-2026-8997 is a medium vulnerability published on May 26, 2026. vifm is vulnerable to a heap buffer overflow during the history merge process when saving the state file (vifminfo.json). This flaw occurs because the application lacks a runtime check on the length of history entries in release builds, potentially allowing a crafted long path or command in the…
When was CVE-2026-8997 disclosed?
CVE-2026-8997 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8997 actively exploited?
CVE-2026-8997 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.3% of all scored CVEs.
What is the CVSS score of CVE-2026-8997?
CVE-2026-8997 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-8997?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8997, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-8997

Explore →

Is Your Infrastructure Affected by CVE-2026-8997?

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

Start Free Scan →Browse All CVEs