---
id: "CVE-2026-124743"
page: "https://infrastack.ai/live/CVE-2026-124743"
kind: "vulnerability"
aliases: ["CVE-2026-124743"]
title: "BusyBox: crafted HFS+ filesystem image can crash volume identification"
severity: "medium"
cvss: 5.5
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["busybox", "embedded", "infrastructure", "linux"]
not_affected_if: ["no-hfs-media", "no-untrusted-storage"]
published_at: "2026-11-11T12:19:48+00:00"
first_seen_at: "2026-11-11T12:27:11+00:00"
updated_at: "2026-11-11T12:28:40+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-124743", "first_seen_at": "2026-11-11T12:27:11+00:00"}]
exploit_sources: []
---

# BusyBox: crafted HFS+ filesystem image can crash volume identification

Link for people: https://infrastack.ai/live/CVE-2026-124743 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- `busybox --help` to confirm BusyBox is present and read the version line
- Check whether any BusyBox build on the system includes HFS+ support (`busybox blkid` or `busybox mount` used on untrusted media)

## Timeline

- 2026-11-11T12:27:11+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-124743

## From 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_