CVE-2026-26157

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-02-11 21:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-11-04 23:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 7.0 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-02-11 21:16 UTC

Last modified

2026-11-04 23:17 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-73

Record status

Deferred

Attack profile CVSS 3.1 · 7.0

Attack vector

Local

Complexity

High

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-26157.md and follow it. Check whether this project is affected by CVE-2026-26157. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge