VulnerabilityPublished 11 Nov 2026

CVE-2026-124743: Red Hat Hardened Images · Divide By Zero

Affects Red Hat Hardened ImagesSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 11 Nov 2026, 11:49 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.

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

Currently, no mitigation or patch meets Red Hat's criteria for ease of use, applicability, or stability. Red Hat advises monitoring their advisory for updates. Exposure is limited due to BusyBox's restricted use in rescue or initramfs environments rather than standard enterprise workflows. Users should avoid processing untrusted HFS+ filesystem images or attaching untrusted storage devices to systems using BusyBox in these contexts.

Description

CVE-2026-124743 is a vulnerability in BusyBox affecting the volume identification component when processing HFS+ filesystem metadata. Improper validation of header values can lead to a divide-by-zero error, causing an application crash and resulting in a local denial of service (DoS). Exploitation requires local access to attach a specially crafted storage device or filesystem image. The impact is limited to DoS without confidentiality or integrity loss. Red Hat notes that BusyBox is typically used only in rescue or initramfs environments, reducing exposure in standard enterprise workflows. No mitigation or patch currently meets Red Hat's criteria for widespread deployment.

Impact

The vulnerability causes a denial of service by crashing the application processing the filesystem metadata due to a divide-by-zero error. It does not impact confidentiality or integrity. Exploitation requires local access and user interaction to mount or process a specially crafted HFS+ filesystem image or storage device. The blast radius is limited to local denial of service or potential out-of-bounds memory read during probing operations. Standard Red Hat Enterprise Linux environments have reduced exposure because BusyBox is not the default utility for filesystem resolution.

Summary

This vulnerability in BusyBox arises from improper validation of header values in HFS+ filesystem metadata during volume identification. An attacker with local access can supply a crafted filesystem image or attach a storage device that triggers a divide-by-zero error, crashing the application and causing a denial of service. The flaw affects Red Hat Hardened Images where BusyBox is present, but exposure is limited since BusyBox is not the default utility provider in Red Hat Enterprise Linux and is mainly used in rescue shells or initramfs. Red Hat rates this vulnerability as moderate severity with a CVSS 3.1 score of 5.5, reflecting local attack vector, low complexity, no privileges required, and user interaction needed.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 11:34 UTC

Technical details

References

Community reviews

Related threats