CVE-2026-124743 · Infrastructure
NO FIX YET
BusyBox's volume identification code does not validate header values in HFS+ filesystems, so a crafted image or attached storage device can crash the process. The result is a denial of service that stops device resolution.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems that run BusyBox and automatically identify or mount removable or untrusted storage, such as embedded devices, appliances, or recovery environments. Systems that never parse foreign HFS+ media can skip it. The sources do not state affected version ranges.
Not affected if no-hfs-media, no-untrusted-storage
Who cares busybox, embedded, linux
busybox --help to confirm BusyBox is present and read the version linebusybox blkid or busybox mount used on untrusted media)No fix yet, per the sources.
A flaw was found in BusyBox. When processing filesystem metadata, the volume identification component does not properly validate header values in HFS+ filesystems. An attacker able to attach a storage device or supply a specially crafted filesystem image can trigger an application crash, resulting in a Denial of Service (DoS) and preventing device resolution.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.