eazip: symlink-target validation checks the wrong argument, allowing extraction path escapes on Windows
Affects eazipSource GCVE Database
CVSS 8.6 High : upgrade to 0.2.7 soon.
Data as of 12 Nov 2026, 08:06 UTC
- Patch
- Available – fixed in 0.2.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:NWhat to do
Upgrade eazip to 0.2.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.ioeazippkg:cargo/eazipOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade eazip to version 0.2.7 or later, which includes a fix that properly validates symlink targets by rejecting backslash and NUL bytes. No other mitigation is required as the fix addresses the root cause. Applications extracting untrusted archives should ensure they use the fixed version to prevent path escape via symlinks on Windows.
Description
A vulnerability in eazip versions 0.2.5 and 0.2.6 allows crafted archives to create symlinks that escape the intended extraction directory on Windows. This occurs because the symlink target validation mistakenly checks the symlink name instead of the target, allowing backslash characters in targets to bypass validation. This can lead to arbitrary filesystem writes outside the extraction directory. The issue was fixed in version 0.2.7.