CVE-2026-8997

Local application crash via fixed-size trie buffer

Published May 22, 2026 · Updated May 22, 2026

Heap buffer overflow in Vifm 0.12.1 through 0.14.3 allows local users to crash the application via an oversized history entry. During vifminfo.json history merging, alloc_string() copies a trie key longer than its fixed PATH_MAX*2 heap buffer because release builds omit the assert() guard. A passive user action that saves state must merge a crafted long path or command; published evidence establishes memory corruption and crashes, not code execution.

CVSS severity4.8
Medium
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Heap buffer overflow in Vifm 0.12.1 through 0.14.3 allows local users to crash the application via an oversized history entry. During vifminfo.json history merging, alloc_string() copies a trie key longer than its fixed PATH_MAX*2 heap buffer because release builds omit the assert() guard. A passive user action that saves state must merge a crafted long path or command; published evidence establishes memory corruption and crashes, not code execution.

The record

CVE
CVE-2026-8997
Published
May 22, 2026
Updated
May 22, 2026
Vendor
Vifm
Product
Vifm
Classifications
CWE-122
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 22, 2026CVE publishedPublication date reported by the CVE source.
  2. May 22, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0.12.1 <=0.14.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Vifm · Vifmversion=0.12.1 <=0.14.3

Published CVSS scores

4.8CERT.PLCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-122Heap-based Buffer Overflow

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo