ant-releases: extracting a release archive can write files outside the destination directory (path traversal / zip-slip)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

`ant-releases` downloads and unpacks release archives from the `safe_network` / `autonomi` repositories. When it extracts an archive, it builds each output path by joining the archive entry's own name onto the destination directory, with no check for `..` or absolute components — a classic "zip-slip" path traversal (CWE-22 / CWE-23). A crafted archive can therefore create or overwrite files outside the intended extraction directory. In `extract_release_archive` (`src/lib.rs`), the ZIP branch does: ```rust let out_path = dest_dir_path.join(file.name()); // raw zip entry name, no containment check if file.name().ends_with('/') { std::fs::create_dir_all(&out_path)?; // dir created outside dest_dir } else { let mut outfile = std::fs::File::create(&out_path)?; // file written outside dest_dir std::io::copy(&mut file, &mut outfile)?; } ```

Proof of concept A one-entry ZIP whose entry name is `../foo_pwned.txt`, passed to `AntReleaseRepoActions::extract_release_archive` (obtained via…

Published by the source

31 Oct 2026, 12:00 UTC

Last modified by the source

2 Nov 2026, 11:30 UTC

Source last checked

3 Nov 2026, 06:10 UTC

1. Revision 1 · created · 3 Nov 2026

   Published from osv record RUSTSEC-2026-0434

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: rustsec-2026-0434

Advisory: `ant-releases`: extracting a release archive can write files outside the destination directory (path traversal / zip-slip)
IDs: rustsec-2026-0434
Record: https://patchnext.com/advisories/rustsec-2026-0434 (revision 1, source checked 3 Nov 2026, 06:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io ant-releases: affected >= 0.0.0-0

## Suggested inspection (read-only)
- crates.io ant-releases: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ant-releases.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0434 (OSV record RUSTSEC-2026-0434 lists affected ranges: crates.io ant-releases >=0.0.0-0)

Commands are suggestions: review each one before running it.