sn-releases: extract_release_archive writes archive entries without a path-traversal check (zip-slip)

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

`SafeReleaseRepoActions::extract_release_archive` builds each output path from the raw archive entry name and writes to it with no traversal check, so a malicious release archive can create directories and write files outside the destination directory, a "zip-slip" / path traversal (CWE-22 / CWE-23). In `src/lib.rs` (`extract_release_archive`, zip branch): ```rust let mut file = archive.by_index(i)?; let out_path = dest_dir_path.join(file.name()); // file.name() is the raw entry name if file.name().ends_with('/') { std::fs::create_dir_all(&out_path)?; // no `..` check } else { let mut outfile = std::fs::File::create(&out_path)?; // writes outside dest std::io::copy(&mut file, &mut outfile)?; } ``` The crate is unmaintained (latest release 0.3.1, 2024-10-22) and no fixed version is available.

Published by the source

29 Oct 2026, 12:00 UTC

Last modified by the source

30 Oct 2026, 11:15 UTC

Source last checked

31 Oct 2026, 06:45 UTC

1. Revision 1 · created · 31 Oct 2026

   Published from osv record RUSTSEC-2026-0427

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

# Patch Next advisory brief: rustsec-2026-0427

Advisory: `sn-releases`: `extract_release_archive` writes archive entries without a path-traversal check (zip-slip)
IDs: rustsec-2026-0427
Record: https://patchnext.com/advisories/rustsec-2026-0427 (revision 1, source checked 31 Oct 2026, 06:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
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 sn-releases: affected >= 0.0.0-0

## Suggested inspection (read-only)
- crates.io sn-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 sn-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-0427 (OSV record RUSTSEC-2026-0427 lists affected ranges: crates.io sn-releases >=0.0.0-0)

Commands are suggestions: review each one before running it.