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

CVE-2026-90954: BusyBox dpkg-deb Path Traversal Vulnerability

CVE-2026-90954 is a path traversal flaw in BusyBox dpkg-deb that allows attackers to write files outside extraction directories via crafted .deb archives. This post covers technical details, impact, and mitigation.

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-90954 Overview

A symlink handling flaw in BusyBox's dpkg-deb archive extraction allows attackers to write files outside the intended extraction directory. The ar archive handler flushes deferred symlinks after each archive member, while the tar, cpio, and unzip handlers flush only after the final member. A crafted .deb archive with two data.tar members can abuse this ordering to materialize an unsafe symlink before the second member is processed. The vulnerability is tracked under CWE-59: Improper Link Resolution Before File Access.

Critical Impact

A user extracting a malicious .deb package with BusyBox can have arbitrary files written to arbitrary filesystem locations, enabling privilege escalation when extraction runs as root.

Affected Products

  • BusyBox dpkg-deb applet (ar archive handler)
  • Linux distributions and embedded systems bundling vulnerable BusyBox builds
  • Container images using BusyBox as their core userland

Discovery Timeline

  • 2026-10-14 - CVE CVE-2026-90954 published to NVD
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2026-90954

Vulnerability Analysis

BusyBox implements multiple archive handlers that share a deferred-symlink safety mechanism. When an archive declares a symlink pointing to an absolute path or a path traversing outside the extraction root, the handler defers creation to prevent subsequent file writes from escaping the target directory. The tar, cpio, and unzip handlers flush these deferred symlinks only after processing the last archive member, keeping the filesystem view safe during extraction.

The ar handler, used by dpkg-deb to parse Debian packages, deviates from this pattern. It flushes deferred symlinks after each archive member rather than at the end. This early-flush behavior reopens the traversal window the deferral mechanism was designed to close.

Root Cause

The root cause is inconsistent lifecycle management of deferred symlinks across archive handlers. The ar handler treats each member as an independent extraction unit and finalizes pending symlinks between members. A Debian package normally contains debian-binary, control.tar, and data.tar members in sequence, but the format permits multiple data.tar entries. Two consecutive data.tar members create an exploitable ordering gap.

Attack Vector

An attacker crafts a .deb archive containing two data.tar members. The first member declares a symlink such as link -> /. BusyBox defers this symlink as unsafe, then flushes it to disk after the first member completes. The second member contains a regular file whose path traverses link, for example link/etc/cron.d/payload. Because the symlink is now live on the filesystem, the write resolves outside the extraction directory and lands in /etc/cron.d/. Exploitation requires local user interaction to extract the crafted package.

Technical details are available in the Red Hat CVE-2026-90954 Advisory and the associated Red Hat Bug Report #2533007.

Detection Methods for CVE-2026-90954

Indicators of Compromise

  • .deb files containing more than one data.tar archive member, which deviates from standard Debian package structure
  • Symlinks in extraction directories pointing to absolute paths such as /, /etc, or /root created by busybox dpkg-deb processes
  • Files written outside the expected extraction root following a busybox dpkg-deb -x or -X invocation

Detection Strategies

  • Inspect .deb archives with ar t package.deb before extraction and flag archives containing multiple data.tar* members
  • Audit filesystem writes performed by busybox processes against the current working directory passed to the extraction command
  • Monitor for unexpected modifications to sensitive paths such as /etc/cron.d/, /etc/sudoers.d/, and ~/.ssh/authorized_keys following package extraction

Monitoring Recommendations

  • Enable auditd rules on execve events for busybox dpkg-deb and correlate with subsequent openat writes outside the target directory
  • Log and alert on symlink creation events where the target is an absolute path during package extraction workflows
  • Track BusyBox versions deployed across container images and embedded devices to identify unpatched instances

How to Mitigate CVE-2026-90954

Immediate Actions Required

  • Avoid extracting untrusted .deb packages with BusyBox dpkg-deb until a patched version is deployed
  • Use the full dpkg-deb from the dpkg package instead of the BusyBox applet where possible
  • Run package extraction as an unprivileged user inside an isolated directory to limit filesystem impact

Patch Information

Refer to the Red Hat CVE-2026-90954 Advisory for distribution-specific patch availability and update instructions. Rebuild container images that bundle BusyBox once upstream fixes are available, and apply vendor updates to embedded systems through standard firmware channels.

Workarounds

  • Validate .deb archive structure with ar t and reject any archive containing multiple data.tar members before invoking BusyBox
  • Extract untrusted packages inside a container, chroot, or ephemeral virtual machine to contain traversal writes
  • Mount the extraction target with nosuid and nodev and restrict write access to sensitive system directories using mandatory access controls

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.