CVE-2026-26157

CVE-2026-26157 is a high-severity vulnerability with a CVSS 3.x base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-73.

Key facts

Description

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.

Frequently asked questions

What is CVE-2026-26157?
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.
How severe is CVE-2026-26157?
CVE-2026-26157 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-26157 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (48th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-26157?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-26157 have an EU (EUVD) identifier?
Yes. CVE-2026-26157 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-7022.
When was CVE-2026-26157 published?
CVE-2026-26157 was published on 2026-02-11 and last updated on 2026-06-30.

References

Other CWE-73 vulnerabilities

Browse all CWE-73 vulnerabilities →