Quick answers
- Is CVE-2026-124742 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124742 being exploited in the wild.
- How severe is CVE-2026-124742?
- Medium severity, with a CVSS score of 5.5, published 11 November 2026.
- Which products and versions are affected?
- BusyBox BusyBox.
- Is there a fix for CVE-2026-124742?
- 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-124742 attacked?
- It is attacked with local access or from the adjacent network, in a software library.
- Am I affected by CVE-2026-124742?
- Check whether you run Busybox. 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
A divide-by-zero condition exists in the volume_id FAT prober when cluster parameters are not properly validated, specifically when a zero sectors_per_cluster value is encountered. The vulnerability is triggered when partition scanning utilities analyze a specially formatted FAT filesystem on a crafted storage device or disk image, causing an unhandled crash. This is a local or adjacent attack requiring the ability to present untrusted block devices.
Affected products
- BusyBox BusyBox
Timeline
- 2026-11-11: disclosed