Arbitrary file modification via unvalidated hardlink targets
Published May 26, 2026 · Updated May 26, 2026
Improper link resolution in BINGOS Archive::Tar before 3.08 allows context-dependent attackers to modify files via crafted tar archives. Archive::Tar::_make_special_file passes each tar header's unvalidated linkname to link(), so an absolute path or .. segment creates an extracted hardlink to a victim inode outside the destination. Hardlink extraction is enabled by default before 3.06 and requires EXTRACT_HARDLINK in 3.06 and 3.07; extraction can overwrite victim contents or alter their mode, owner, and timestamps.
Summary
What happened
Improper link resolution in BINGOS Archive::Tar before 3.08 allows context-dependent attackers to modify files via crafted tar archives. Archive::Tar::_make_special_file passes each tar header's unvalidated linkname to link(), so an absolute path or .. segment creates an extracted hardlink to a victim inode outside the destination. Hardlink extraction is enabled by default before 3.06 and requires EXTRACT_HARDLINK in 3.06 and 3.07; extraction can overwrite victim contents or alter their mode, owner, and timestamps.
The record
- CVE
- CVE-2026-42497
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- BINGOS
- Product
- Archive::Tar
- Classifications
- CWE-732, CWE-59
- 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