{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-8997 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-8997 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: There is no known exploitation of CVE-2026-8997 in the wild and no public exploit code.\n\nAffected product: vifm. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-8997/ (Markdown: https://insights.sbomify.com/CVE-2026-8997/index.md)","id":"CVE-2026-8997","markdown":"https://insights.sbomify.com/CVE-2026-8997/index.md","name":"CVE-2026-8997","record":{"aliases":["DEBIAN-CVE-2026-8997","GHSA-3623-vc46-pwpv","UBUNTU-CVE-2026-8997","openSUSE-SU-2026:10928-1"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"vifm file manager","requires_auth":"none","summary":"A heap buffer overflow in vifm allows attackers to cause crashes or execute code via crafted history entries during state file saving.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"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.\nReleases from 0.12.1 to 0.14.3 (including) are considered vulnerable. This issue was fixed in commit 23063c7","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Heap Buffer Overflow in vifm","id":"CVE-2026-8997","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"IBM WebSphere eXtremes Scale is affected by uncontrolled resource consumption when XDF is enabled","id":"CVE-2026-9002"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["0.14.4-1.1"],"introduced":["0"],"last_affected":[],"package":"vifm","purl":"pkg:rpm/opensuse/vifm\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:10928-1"}],"prev":{"headline":"Missing authorization in Backup and Staging by WP Time Capsule","id":"CVE-2026-8996"},"products":["vifm"],"published":"2026-05-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-22","vendors":["vifm"]},"summary":"A heap buffer overflow in vifm allows attackers to cause crashes or execute code via crafted history entries during state file saving.","url":"https://insights.sbomify.com/CVE-2026-8997/"}