# CVE-2026-124746: BusyBox integer overflow in volume_id

Source: https://junglewise.ai/threats/cve-2026-124746-a-flaw-was-found-in-busybox-an-integer-overflow-occurs-in-the  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-11. Updated: 2026-11-11  
License: CC BY 4.0 with a link back

CVE-2026-124746 · Severity: medium · CVSS 5.5 · Published 2026-11-11

BusyBox is a lightweight toolkit used in embedded systems and minimal Linux environments to perform system operations like mounting storage devices. An integer overflow in the volume_id component can crash the application when it examines a specially crafted filesystem image, preventing the system from accessing or mounting storage devices. This vulnerability affects minimal installations and specialized containers that rely on BusyBox utilities to probe untrusted storage media.

Technologies: [BusyBox](https://junglewise.ai/threats/technologies/x-busybox).

## Quick answers

**Is CVE-2026-124746 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-124746 being exploited in the wild.

**How severe is CVE-2026-124746?** Medium severity, with a CVSS score of 5.5, published 11 November 2026.

**Which products and versions are affected?** BusyBox <UNKNOWN>.

**Is there a fix for CVE-2026-124746?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-124746 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-124746?** Check whether you run BusyBox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An integer overflow in the volume_id_get_buffer() function occurs when calculating buffer boundaries during filesystem metadata probing, triggered by an offset and length wraparound. The vulnerability requires a local attack vector involving user interaction with an attacker-supplied storage device or filesystem image. Exploitation causes an application crash (denial of service) with no information disclosure or code execution.

## Affected products

- BusyBox <UNKNOWN>

## Timeline

- 2026-11-11: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-124746](https://access.redhat.com/security/cve/CVE-2026-124746)

## Related threats

- [BusyBox tar hardlink resolution path traversal](https://junglewise.ai/threats/cve-2026-124745-a-flaw-was-found-in-busybox-when-extracting-an-archive-the-tar)
- [BusyBox cpio hardlink path traversal vulnerability](https://junglewise.ai/threats/cve-2026-124744-a-flaw-was-found-in-busybox-when-extracting-files-using-the-cpio)
- [BusyBox divide-by-zero in HFS+ filesystem parsing](https://junglewise.ai/threats/cve-2026-124743-a-flaw-was-found-in-busybox-when-processing-filesystem-metadata)
- [BusyBox udhcpc6 use-after-free in DHCPv6 client](https://junglewise.ai/threats/cve-2026-124740-a-flaw-was-found-in-busybox-s-udhcpc6-dhcpv6-client-a-malicious)
- [BusyBox httpd authentication bypass via pre-compressed files](https://junglewise.ai/threats/cve-2026-124738-a-flaw-was-found-in-busybox-when-the-http-daemon-httpd-has-pre)