CVE-2026-26157: Busybox: busybox: arbitrary file overwrite and potential code execution via incomplete path sanitization
A flaw was found in BusyBox. Incomplete path sanitization in its archive extraction utilities allows an attacker to craft malicious archives that when extracted, and under specific conditions, may write to files outside the intended directory. This can lead to arbitrary file overwrite, potentially enabling code execution through the modification of sensitive system files.
Other sources
Affects: BusyBox v1.36.1 and v1.37.0 (likely affects earlier versions too) CVSS: 8.6 (HIGH) Component: stripunsafeprefix() function in archive extraction utilities (tar, unzip, rpm, ar, dpkg)
Description: Incomplete path sanitization fails to detect trailing ".." components in filenames (e.g., "logs/data/.."), allowing files to be written outside the intended extraction directory when the current working directory matches the target location. An attacker can craft malicious archives that overwrite arbitrary files within the extraction directory scope.
Impact: Arbitrary file overwrite, potential code execution through modification of shell configuration files, cron jobs, or other sensitive files.
— Red Hat
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-26157?
The severity of CVE-2026-26157 is classified as high due to arbitrary file overwrite and potential code execution risks.
How do I fix CVE-2026-26157?
To fix CVE-2026-26157, it is recommended to update BusyBox to the latest version beyond 1.37.0.
What versions of BusyBox are affected by CVE-2026-26157?
BusyBox versions from 1.36.1 to 1.37.0 are affected by CVE-2026-26157.
What are the potential impacts of CVE-2026-26157?
The potential impacts of CVE-2026-26157 include arbitrary file overwriting and executing malicious code.
How does CVE-2026-26157 allow file overwrite?
CVE-2026-26157 allows file overwrite due to incomplete path sanitization in BusyBox's archive extraction utilities.