The vulnerability stemmed from improper symlink validation in archive extraction logic. The original code checked for absolute paths and '..' prefixes in symlink targets (nameOfLinkedFile), but didn't account for cases where relative paths could be combined with parent directory locations to escape the output path. The patch introduced _isValidSymLink which properly resolves and checks the full path using path normalization and isWithin checks. Both extractArchiveToDisk and extractFileToDisk contained the vulnerable validation pattern before the patch, as shown in the commit diff where the old checks (startsWith '/' or '..') were replaced with the new validation function.