CVE-2026-124743VulnerabilityPublished 11 Nov 2026

BusyBox · CWE-369

Source GCVE Database

Compare

Authoritative record:CVE-2026-124743· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 11 Nov 2026, 13:32 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	5.5

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-gjcv-9jxm-vqjv

What to do

Affected software

Product	Affected	Fixed in
Red Hat Enterprise Linux 6busybox	Affected–	Fixed in–
Red Hat Hardened Imagesbusybox	Affected–	Fixed in–

AI-suggested

Red Hat states that no mitigation is currently available or meets their criteria for ease of use, applicability, or stability. Since BusyBox is typically used in limited environments such as rescue shells or initramfs, standard enterprise workflows relying on other tools reduce exposure. Users should monitor Red Hat advisories for any future fixes or mitigations. No urgent action is required beyond awareness of the limited exposure and impact.

Description

A vulnerability in BusyBox's volume identification component for HFS+ filesystems allows improper validation of header values. An attacker with local access to attach a storage device or supply a crafted filesystem image can cause an application crash, resulting in a denial of service (DoS) that prevents device resolution. This issue is rated as moderate severity by Red Hat, primarily causing local DoS with no confidentiality or integrity impact. BusyBox is typically used in rescue or initramfs environments rather than as a default core utility in Red Hat Enterprise Linux, limiting exposure.

Impact

The impact is a local denial of service caused by application crash when processing specially crafted HFS+ filesystem metadata. There is no impact on confidentiality or integrity. The vulnerability requires local access to attach or supply a malicious storage volume. Because BusyBox is not the default core utility in Red Hat Enterprise Linux and is mainly used in limited environments, the exposure is significantly reduced. No known exploits are reported in the wild.

Summary

CVE-2026-124743 is a vulnerability in BusyBox where the volume identification component does not properly validate header values in HFS+ filesystem metadata. This flaw can be triggered by an attacker able to attach a storage device or supply a specially crafted filesystem image, causing an application crash and denial of service. The vulnerability is classified under CWE-369 (Divide By Zero) and results in a crash due to a divide-by-zero condition or heap over-read during probing operations. Red Hat notes that BusyBox is not the default provider of core utilities in their enterprise Linux and is mostly limited to rescue shells or initramfs environments, reducing the blast radius.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 13:32 UTC

WeaknessesCWE-369

Technical details

References

Community reviews

Related threats