BusyBox EUVD-2026-44850

Triggering requires attacker-controlled input to reach BusyBox 1.38.0's ash shell field-splitting path (ifsbreakup() in shell/ash.c) - i.e., data that undergoes IFS-based word splitting during shell expansion. The practical limiting factor is the delivery path: the attacker must be able to invoke or feed input into an ash shell, which in most deployments means local shell access or an application/service that forwards untrusted input into a BusyBox shell script. The NVD vector marks this AV:N/PR:N (remote, unauthenticated), but that is not corroborated by the description and holds only where a network-facing component pipes untrusted input directly into ash; on a default embedded system without such a bridge, exploitation is effectively local. Impact is limited to a process crash (availability only) - no code execution or data disclosure is indicated.

The signals are mixed and lean toward lower real-world priority than the 7.5 CVSS suggests. The NVD vector (AV:N/AC:L/PR:N/UI:N/A:H) implies a trivially reachable remote availability attack, but the description describes a heap overflow in an interactive/script shell (ash) triggered by 'crafted input' - reaching ifsbreakup() normally requires the attacker to supply input to a shell they can already invoke, which is typically a local vector. This is a material conflict: CVSS indicates a network vector, but the described mechanism implies local or context-dependent access - verify with the vendor. EPSS is low (0.16%, 6th percentile), there is no KEV listing and no public exploit identified at time of analysis, and impact is confined to availability (C:N/I:N) - a crash, not code execution or data compromise. No SSVC decision data was provided. Net: a genuine memory-safety bug worth patching on exposed embedded/container fleets, but not an emergency; the headline CVSS overstates the practical exposure absent a scenario where untrusted network input flows directly into ash.

An attacker who can supply input to a BusyBox ash shell - for example a script or command line whose field-splitting operates on attacker-influenced data - provides a crafted string that overflows the heap buffer in ifsbreakup(), corrupting memory and crashing the shell. In a deployment where an exposed service passes untrusted input into an ash script, this could translate into a repeatable denial of service against that component. No public exploit code has been identified at time of analysis.