{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27117 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-27117 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27117 is a medium-severity path traversal vulnerability in rikyoz bit7z, published on 24 Feb 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-27117 and fix it if it is affected.\n\nWhat it is: CVE-2026-27117 is a medium-severity path traversal vulnerability in rikyoz bit7z, published on 24 Feb 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-27117 in the wild and no public exploit code.\n\nAffected product: rikyoz bit7z. 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-27117/ (Markdown: https://insights.sbomify.com/CVE-2026-27117/index.md)","id":"CVE-2026-27117","markdown":"https://insights.sbomify.com/CVE-2026-27117/index.md","name":"CVE-2026-27117","record":{"aliases":["GHSA-qvjh-hhw4-3gx9"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"C++ archive library","requires_auth":"none","summary":"Attackers can write arbitrary files outside the extraction directory via malicious archives, potentially overwriting binaries or configs in applications using bit7z.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"bit7z","vendor":"rikyoz"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-36","name":"Absolute Path Traversal"},{"id":"CWE-23","name":"Relative Path Traversal"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"bit7z is a cross-platform C++ static library that allows the compression/extraction of archive files. Prior to version 4.0.11, a path traversal vulnerability (\"Zip Slip\") exists in bit7z's archive extraction functionality. The library does not adequately validate file paths contained in archive entries, allowing files to be written outside the intended extraction directory through three distinct mechanisms: relative path traversal, absolute path traversal, and symbolic link traversal. An attacker can exploit this by providing a malicious archive to any application that uses bit7z to extract untrusted archives. Successful exploitation results in arbitrary file write with the privileges of the process performing the extraction. This could lead to overwriting of application binaries, configuration files, or other sensitive data. The vulnerability does not directly enable reading of file contents; the confidentiality impact is limited to the calling application's own behavior after extraction. However, applications that subsequently serve or display extracted files may face secondary confidentiality risks from attacker-created symlinks. Fixes have been released in version 4.0.11. If upgrading is not immediately possible, users can mitigate the vulnerability by validating each entry's destination path before writing. Other mitigations include running extraction with least privilege and extracting untrusted archives in a sandboxed directory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"bit7z has a path traversal vulnerability","id":"CVE-2026-27117","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Cache poisoning in @sveltejs/adapter-vercel","id":"CVE-2026-27118"},"packages":[],"prev":{"headline":"Vikunja has Reflected HTML Injection via filter Parameter in Projects Module","id":"CVE-2026-27116"},"products":["bit7z"],"published":"2026-02-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-02-26","vendors":["rikyoz"]},"summary":"Attackers can write arbitrary files outside the extraction directory via malicious archives, potentially overwriting binaries or configs in applications using bit7z.","url":"https://insights.sbomify.com/CVE-2026-27117/"}