Skip to main content
Vulnerability Database/CVE-2026-92205

CVE-2026-92205: BusyBox libarchive Path Traversal Vulnerability

CVE-2026-92205 is a path traversal flaw in BusyBox libarchive that enables attackers to create arbitrary files via malicious archives. This post covers technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-92205 Overview

CVE-2026-92205 is a directory traversal vulnerability in the libarchive component of BusyBox. The flaw stems from improper validation of user-supplied paths before using them in file operations. Attackers can abuse symbolic links inside crafted archives to write files outside the intended extraction directory. Exploitation requires user interaction, such as opening a malicious archive or visiting a page that triggers extraction. Successful exploitation enables arbitrary file creation in the context of the current user, which can lead to code execution or configuration tampering. The issue was reported through the Zero Day Initiative as ZDI-CAN-27556 and tracked in advisory ZDI-26-705.

Critical Impact

Arbitrary file creation under the current user's privileges, enabling potential persistence, configuration overwrite, or follow-on code execution on affected BusyBox installations.

Affected Products

  • BusyBox (libarchive component)
  • Embedded Linux systems bundling vulnerable BusyBox builds
  • Appliances and IoT firmware relying on BusyBox archive extraction utilities

Discovery Timeline

  • 2026-10-21 - CVE-2026-92205 published to the National Vulnerability Database (NVD)
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-92205

Vulnerability Analysis

The vulnerability resides in BusyBox's libarchive component, which handles archive parsing and extraction. During extraction, the component processes entry paths and symbolic link targets without sufficient canonicalization. An archive crafted with a symlink pointing outside the extraction root can redirect subsequent file write operations to attacker-chosen locations. The result is arbitrary file creation anywhere the invoking user has write permission. The weakness is classified under CWE-22, Improper Limitation of a Pathname to a Restricted Directory.

Root Cause

The root cause is missing validation of resolved paths before file operations occur. The extractor trusts both archive entry names and symlink targets. It does not verify that the final resolved path remains inside the destination directory. This classic symlink traversal pattern allows attacker-controlled paths to escape the sandboxed extraction root.

Attack Vector

Exploitation is local and requires user interaction. The target user must open a malicious archive or visit a page that triggers automatic extraction through BusyBox utilities such as tar or cpio wrappers built against the vulnerable libarchive. Once extraction begins, the crafted symlink redirects a follow-up write to a sensitive location, such as a shell startup file, a cron directory, or a SUID binary path. No authentication is required, but privileges are limited to those of the invoking user.

No verified public exploit code is available at this time. See the Zero Day Initiative Advisory ZDI-26-705 for technical details.

Detection Methods for CVE-2026-92205

Indicators of Compromise

  • Archive files containing symbolic links whose targets use ../ sequences or absolute paths outside the extraction directory.
  • Unexpected files appearing in sensitive locations such as /etc/, ~/.ssh/, ~/.bashrc, or cron directories after archive extraction.
  • Process telemetry showing BusyBox tar, cpio, or unzip invocations writing to paths outside the working directory.

Detection Strategies

  • Hunt for BusyBox extraction processes followed by file writes to directories outside the archive destination.
  • Inspect archive contents prior to extraction, flagging entries where symlink targets resolve outside the extraction root.
  • Correlate archive extraction events with modifications to shell initialization files, authorized key files, and scheduled task directories.

Monitoring Recommendations

  • Enable file integrity monitoring on /etc/, user home directories, and cron paths on systems running BusyBox.
  • Log command-line arguments for BusyBox invocations and alert on extraction into privileged or user-sensitive directories.
  • Monitor firmware and container images for BusyBox builds that have not been updated against CVE-2026-92205.

How to Mitigate CVE-2026-92205

Immediate Actions Required

  • Inventory all systems, firmware, and containers that bundle BusyBox with libarchive support.
  • Restrict archive extraction to least-privileged accounts and non-sensitive working directories.
  • Validate archives from untrusted sources before extraction, rejecting entries containing symlinks that escape the destination.

Patch Information

Refer to the Zero Day Initiative Advisory ZDI-26-705 for upstream remediation status. Rebuild and redeploy BusyBox from a fixed source release once the maintainers publish a patched version. Embedded and appliance vendors should ship updated firmware images incorporating the fixed BusyBox build.

Workarounds

  • Extract untrusted archives inside sandboxed environments such as containers, chroot jails, or dedicated unprivileged accounts.
  • Pre-scan archives and reject any entry whose resolved path or symlink target leaves the intended extraction directory.
  • Disable automatic extraction features in applications that invoke BusyBox utilities on user-supplied archives.
bash
# Example: safely inspect archive entries before extraction
busybox tar -tvf untrusted.tar | awk '$1 ~ /^l/ {print "symlink:", $0}'

# Example: extract inside an unprivileged, isolated directory
install -d -m 700 /tmp/sandbox_extract
sudo -u nobody busybox tar -xf untrusted.tar -C /tmp/sandbox_extract

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.