CVE-2026-42496: BINGOS Archive::Tar · Link Following
Affects BINGOS Archive::TarSource CVE Database V5
Not known to be exploited · CVSS 9.1 Critical : upgrade to 3.08 as a priority.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.08
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade Archive::Tar and Archive-Tar to 3.08.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BINGOSArchive::Tar | Affected
| Fixed in
|
GitHubArchive-Tarpkg:github/Archive-TarOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Red Hat has issued security advisories and updates addressing this vulnerability. Updated packages for perl-Archive-Tar are available for Red Hat Enterprise Linux 10 and related variants. Users should apply these official patches to remediate the issue. Refer to Red Hat advisory RHSA-2026:30857 and the linked article https://access.redhat.com/articles/11258 for update instructions. Patch status is confirmed by the vendor advisories. No alternative mitigations are specified.
Description
Archive::Tar versions before 3.08 for Perl extract symlinks with attacker controlled targets outside the extraction directory. _make_special_file() passes the tar header's linkname to symlink() without validating it against absolute paths or .. segments. The secure-extract mode check that guards regular file extraction does not cover the symlink target. A subsequent open through the extracted name reads or writes the attacker chosen path.
References
- github.com/jib/archive-tar-new/commit/17c873492a05eddc0de18c1485e0b2cccd5a9158.patch (opens in a new tab)
- metacpan.org/release/BINGOS/Archive-Tar-3.08/changes (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-42497 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-42496 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2481314 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42496.json (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:30857 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:30851 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:30856 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:30852 (opens in a new tab)