Live › vulnerability › CVE-2026-92205
Go to dashboardBusyBox's libarchive component does not validate user-supplied paths before file operations, so a crafted archive can make BusyBox create files at locations outside the intended directory. An attacker gets arbitrary file creation in the context of the current user, and only after the victim opens a malicious file or visits a malicious page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
busybox --help on the host to confirm BusyBox is installed and read the version lineEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
BusyBox libarchive Symlink Directory Traversal Arbitrary File Creation Vulnerability. This vulnerability allows remote attackers to create arbitrary files on affected installations of BusyBox. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.
The specific flaw exists within the libarchive component. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to create files in the context of the current user. Was ZDI-CAN-27556.
This page as .md · .json · in your agent: get_signal("CVE-2026-92205")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.