Red Hat Hardened Images
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Fixed in 1.37.0-7.2.hum1
Mitigation
Upgrade Red Hat Hardened Images to 1.37.0-7.2.hum1 or later.
Workaround
As a prevention measure, avoid extracting archives from untrusted sources using BusyBox utilities. If extraction of untrusted archives is necessary, perform it within a highly isolated and restricted environment, such as a container with a read-only root filesystem and minimal privileges, to limit the potential impact of arbitrary file overwrites.
References
Timeline
Days relative to CVE publicationFirst public PoC 77 days after publication; not in CISA KEV. First PoC: BusyBox 1.37.0 - Path Traversal (Exploit-DB, 30 Apr 2026).
PoC repositories
Found on GitHub.1 suspicious or fake
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| calilkhalil/research | 11 Feb 2026 −2 h | 1 | Fake |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| Exploit-DB | BusyBox 1.37.0 - Path Traversal | 30 Apr 2026 | 14 Nov 2026 |