CVE-2026-26158: Busybox: busybox: arbitrary file modification and privilege escalation via unvalidated tar archive entries
A flaw was found in BusyBox. This vulnerability allows an attacker to modify files outside of the intended extraction directory by crafting a malicious tar archive containing unvalidated hardlink or symlink entries. If the tar archive is extracted with elevated privileges, this flaw can lead to privilege escalation, enabling an attacker to gain unauthorized access to critical system files.
Security readout for executives and security teams
Plain-English summary
A malicious tar archive can trick BusyBox extraction into changing files outside the chosen folder. If a privileged process extracts that archive, important system files could be modified, creating a path to privilege escalation. The risk is highest where automated or admin workflows extract untrusted archives as root.
Executive priority
Treat this as a high-priority hygiene and image-update issue, especially for build pipelines, appliances, and privileged automation. It is not currently evidenced as exploited, but it can affect core system integrity when unsafe archive extraction is present.
Technical view
The flaw involves unvalidated hardlink or symlink entries during BusyBox tar extraction, enabling arbitrary file modification outside the intended destination. The provided CVSS is 7.0 high with local attack vector, high complexity, no privileges required, and user interaction required.
Likely exposure
Confirmed affected scope in the bundle includes Red Hat Hardened Images with busybox-main 1.37.0-7.2.hum1. Red Hat Enterprise Linux 6 is listed with unknown status. Siemens has an advisory reference, but affected Siemens product details are not provided in this bundle.
Exploitation context
The CVE is not marked as CISA KEV, and the bundle provides no evidence of active exploitation. Exploitation requires a crafted archive to be extracted, and business impact depends on whether extraction happens with elevated privileges or in sensitive automation.
Researcher notes
Focus validation on BusyBox tar behavior with archive entries that resolve outside the extraction root. Do not assume broad BusyBox exposure beyond listed products without vendor confirmation. The bundle points to an upstream BusyBox archival commit and Red Hat tracking resources.
Mitigation direction
Apply vendor-provided BusyBox or image updates when available.
Review RHSA-2026:13831 for Red Hat remediation guidance.
Do not extract untrusted tar archives with elevated privileges.
Use isolated, least-privilege extraction workflows for archives.
Check Siemens SSA-253495 if Siemens products are in scope.
Validation and detection
Inventory BusyBox versions and packages across images and systems.
Check for busybox-main 1.37.0-7.2.hum1 in Red Hat Hardened Images.
Identify automated workflows that extract tar archives as root.
Confirm whether RHEL 6 exposure remains unknown in vendor guidance.
Track Red Hat VEX and advisory updates for status changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
3ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-73 · source CWE mapping
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.