CVE-2026-42496
Archive::tar path traversal
- Published26 May 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:30851
- https://access.redhat.com/errata/RHSA-2026:30852
- https://access.redhat.com/errata/RHSA-2026:30856
- https://access.redhat.com/errata/RHSA-2026:30857
- https://access.redhat.com/security/cve/CVE-2026-42496
- https://bugzilla.redhat.com/show_bug.cgi?id=2481314
- https://github.com/jib/archive-tar-new/commit/17c873492a05eddc0de18c1485e0b2cccd5a9158.patch
- https://metacpan.org/release/BINGOS/Archive-Tar-3.08/changes
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42496.json
- https://www.cve.org/CVERecord?id=CVE-2026-42497
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-42496 being actively exploited?
CVE-2026-42496 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.43%.
How severe is CVE-2026-42496?
CVE-2026-42496 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.43% probability of exploitation.
Which products are affected by CVE-2026-42496?
Affected products include Archive::tar.
How do I fix CVE-2026-42496?
Upgrade affected software to a fixed version, for example Archive::tar 3.08 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-42496 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.