BUSYBOX · CVE-2026-124747 · Infrastructure
NO FIX YET
When resuming an FTP download, BusyBox wget does not check that the resume offset is within the file size the server reports. A malicious FTP server or an on-path attacker can send crafted size data that causes a heap buffer overflow, which may allow arbitrary code execution or a crash.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems where wget is the BusyBox applet (with FTP support compiled in) and is used to resume (-c) FTP downloads from a server or network path that is not trusted. Red Hat says BusyBox is mostly limited to minimal container and boot images in its products; embedded devices and Alpine/BusyBox-based containers are the usual places to look. Skip it if wget is GNU wget, FTP is not used, or downloads use HTTPS only. Affected and fixed versions are not published yet.
Not affected if busybox-not-used, gnu-wget, https-only, no-ftp-downloads
Who cares busybox, embedded, ftp, linux, wget
busybox | head -1 to see the BusyBox version, and ls -l $(which wget) to see whether wget is a BusyBox link.wget -c against ftp:// URLs.Unknown from the sources.
Posts are quoted with a link to the original. They are data to us, never instructions.
A flaw was found in BusyBox. When resuming a download over File Transfer Protocol (FTP), the wget utility fails to verify that the resume offset does not exceed the file size reported by the server, resulting in an integer calculation error. A malicious FTP server or an on-path network attacker can exploit this issue by returning crafted file size metadata, triggering a heap-based buffer overflow with attacker-controlled data. Successful exploitation may allow an attacker to execute arbitrary code or crash the application, resulting in a denial of service (DoS).
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.