CVE-2026-42496: Symlink Path Traversal in Perl Archive::Tar
- Vendor
- Archive::Tar Project
Perl Archive::Tar versions before 3.08 allow extraction of symbolic links with attacker-controlled targets outside the extraction directory. The _make_special_file() function passes the tar header's linkname value to symlink() without rejecting absolute paths or parent-directory traversal segments. Secure-extract checks protecting regular file extraction do not validate symbolic-link targets. A subsequent open through an extracted symbolic link can therefore read or write an attacker-selected path outside the extraction directory.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can expose sensitive files or modify files outside the intended extraction directory, subject to the filesystem permissions of the process following the symbolic link. The vulnerability has high confidentiality and integrity impacts. Extraction alone creates the unsafe symbolic link; accessing or modifying the external target requires a subsequent operation that follows it.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid extracting untrusted archives or reject symbolic-link entries before extraction. If extraction is necessary, use an isolated, least-privileged environment without access to sensitive files. Do not rely solely on secure-extract mode, because its regular-file checks do not validate symbolic-link targets.
Remediation
Patch, then assume compromise.
Upgrade Archive::Tar to version 3.08 or later, or install the distribution-provided security update containing the fix. Update affected perl-Archive-Tar packages and any vulnerable bundled copies used by applications.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-42496 exploited in the wild?
- As of Nov 13, 2026, Mallory has no reports of CVE-2026-42496 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-42496?
- As of Nov 13, 2026, Mallory has found no public exploit for CVE-2026-42496.
- Is there a patch for CVE-2026-42496?
- Upgrade Archive::Tar to version 3.08 or later, or install the distribution-provided security update containing the fix. Update affected perl-Archive-Tar packages and any vulnerable bundled copies used by applications.
- What products are affected by CVE-2026-42496?
- Archive::Tar Project Archive::Tar.
- How severe is CVE-2026-42496?
- CVE-2026-42496 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 0.50% (44th percentile) as of Nov 13, 2026.
Recent activity
52 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.