PatchSiren cyber security CVE debrief
CVE-2026-108119 Red Hat CVE debrief
CVE-2026-108119 is a vulnerability in the BusyBox tar applet that allows for tar extraction-root escape via deferred symlink/hardlink creation, potentially leading to privilege escalation or arbitrary code execution. The vulnerability has a CVSS score of 6.3 and is classified as MEDIUM severity. It was published on October 9, 2026, and has not been modified since then.
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 6
- CVSS
- MEDIUM 6.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-09
- Original CVE updated
- 2026-10-09
- Advisory published
- 2026-10-09
- Advisory updated
- 2026-10-09
Who should care
Defenders responsible for BusyBox installations, particularly in environments where elevated privileges are involved, should assess exposure and prioritize verification and patching.
Why it matters
CVE-2026-108119 is a vulnerability in the BusyBox tar applet that allows for tar extraction-root escape via deferred symlink/hardlink creation, potentially leading to privilege escalation or arbitrary code execution. Defenders should prioritize verifying and patching BusyBox installations, particularly in environments where elevated privileges are involved.
- Potential privilege escalation
- Potential arbitrary code execution
- Need for verification of BusyBox installations
- Need for monitoring of suspicious tar extraction activity
Technical summary
The BusyBox tar applet's deferred link-creation handling for symlink and hardlink entries with unsafe-looking targets does not validate that the resolved destination remains inside the extraction directory once the deferred link is created. This allows an attacker to craft a tar archive using a symlink target of exactly '..' combined with a deferred hardlink to create a new file outside the extraction directory, or reuse an extraction directory across two archives to replace an existing file outside it.
Defensive priority
Defenders should prioritize verifying and patching BusyBox installations, particularly in environments where elevated privileges are involved.
Recommended defensive actions
- Verify and patch BusyBox installations
- Review and update extraction directory permissions
- Monitor for suspicious tar extraction activity
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The vulnerability is caused by the tar applet's deferred link-creation handling for symlink and hardlink entries with unsafe-looking targets not validating that the resolved destination remains inside the extraction directory once the deferred link is created.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-108119 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-108119
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-108119 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-108119
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Busybox: busybox: tar extraction-root escape via deferred symlink/hardlink creation bypasses cve
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/108xxx/CVE-2026-108119.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/security/cve/CVE-2026-108119
Supplemental source - vdb-entry, x_refsource_REDHAT
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.