File read and write via unchecked symlink targets
Published May 26, 2026 · Updated May 26, 2026
Path traversal in BINGOS Archive::Tar before 3.08 allows remote attackers to read or write files via a crafted tar archive. Archive::Tar::_make_special_file passes the header linkname directly to symlink without rejecting absolute paths or parent-directory segments. The flaw is reached when an application extracts an attacker-supplied archive and later opens the extracted symlink name.
Summary
What happened
Path traversal in BINGOS Archive::Tar before 3.08 allows remote attackers to read or write files via a crafted tar archive. Archive::Tar::_make_special_file passes the header linkname directly to symlink without rejecting absolute paths or parent-directory segments. The flaw is reached when an application extracts an attacker-supplied archive and later opens the extracted symlink name.
The record
- CVE
- CVE-2026-42496
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- BINGOS
- Product
- Archive::Tar
- Classifications
- CWE-22, CWE-59, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.08
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo