CVE-2026-8997 Heap Buffer Overflow in vifm

Medium 4.8 Published Updated

A heap buffer overflow in vifm allows attackers to cause crashes or execute code via crafted history entries during state file saving.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-8997?

CVE-2026-8997 is a medium-severity memory corruption vulnerability in vifm, published on 22 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

Official description

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

Weakness: CWE-122

Which versions are affected by CVE-2026-8997?

Linux distribution packages (1)
vifm openSUSE:TumbleweedAll versions0.14.4-1.1

How do I fix CVE-2026-8997?

Apply the vendor's patch.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-8997 being exploited?

There is no known exploitation of CVE-2026-8997 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2026-8997, GHSA-3623-vc46-pwpv, UBUNTU-CVE-2026-8997, openSUSE-SU-2026:10928-1.

Is CVE-2026-8997 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free