Quick answers
- Is CVE-2026-108119 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108119 being exploited in the wild.
- How severe is CVE-2026-108119?
- Medium severity, with a CVSS score of 6.3, published 9 October 2026.
- Which products and versions are affected?
- BusyBox <UNKNOWN>.
- Is there a fix for CVE-2026-108119?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-108119 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-108119?
- Check whether you run BusyBox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The tar applet's deferred link-creation mechanism fails to validate that resolved symlink and hardlink destinations remain within the extraction directory after the link is created. An attacker can exploit this by combining a symlink target of '..' with a deferred hardlink to escape the extraction directory and create files outside it, or reuse extraction directories between archives to overwrite external files. The vulnerability requires archive extraction, potentially with elevated privileges.
Affected products
- BusyBox <UNKNOWN>
Timeline
- 2026-10-09: disclosed