Out-of-directory symlink creation via archive extraction
Published Jan 29, 2026 · Updated Jan 29, 2026
Path traversal in Chainguard malcontent 1.8.0 through 1.20.2 allows attackers to create out-of-directory symlinks via crafted archives. The archive handler passes the symlink target and location to handleSymlink in the wrong order and fails to verify that targets resolve inside the extraction directory. Exploitation requires malcontent to scan a crafted tar or deb archive and permits filesystem links to be placed beyond the temporary extraction boundary.
Summary
What happened
Path traversal in Chainguard malcontent 1.8.0 through 1.20.2 allows attackers to create out-of-directory symlinks via crafted archives. The archive handler passes the symlink target and location to handleSymlink in the wrong order and fails to verify that targets resolve inside the extraction directory. Exploitation requires malcontent to scan a crafted tar or deb archive and permits filesystem links to be placed beyond the temporary extraction boundary.
The record
- CVE
- CVE-2026-24846
- Published
- Jan 29, 2026
- Updated
- Jan 29, 2026
- Vendor
- Chainguard
- Product
- malcontent
- Classifications
- CWE-22, CWE-683, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2026CVE publishedPublication date reported by the CVE source.
- Jan 29, 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=>= 1.8.0, < 1.20.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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