malcontent could be made to create symlinks outside the intended extraction directory when scanning a specially crafted tar or deb archive. The handleSymlink function received arguments in the wrong order, causing the symlink target to be used as the symlink location. Additionally, symlink targets were not validated to ensure they resolved within the extraction directory.
Fixes: - Swap handleSymlink arguments; validate symlink location - Validate symlink targets resolve within extraction directory
Acknowledgements
Thank you to Oleh Konko from 1seal for discovering and reporting this issue.
{
"nvd_published_at": "2026-01-29T22:15:54Z",
"cwe_ids": [
"CWE-22",
"CWE-683"
],
"github_reviewed_at": "2026-01-29T22:05:15Z",
"severity": "MODERATE",
"github_reviewed": true
}