CVE-2026-124744

Busybox: cpio hardlink target not sanitized under feature_path_traversal_protection

  • Medium 6.3

Description

A flaw was found in BusyBox. When extracting files using the cpio utility with path traversal protection enabled, hardlink target paths are not properly sanitized. By tricking a user or automated process into extracting a crafted archive, an attacker can create hardlinks that point to files outside the intended extraction directory. This issue may allow an attacker to modify or overwrite arbitrary files outside the target directory during subsequent extraction operations.

Key facts

Published
11 Nov 2026
Last changed
12 Nov 2026
Assigned by
redhat
EPSS
0.15% likely to be exploited in the next 30 days, higher than 4.226% of CVEs (scores for 15 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.3CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

What to do

  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 6
  • Default status: unaffected
Red HatRed Hat Hardened Images
  • Default status: affected

Timeline

  1. 25 Oct 2026 Reported to Red Hat.
  2. 11 Nov 2026 Made public.
  3. 11 Nov 2026 Published

Weakness

References