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

Advisory record · `RUSTSEC-2026-0427`

- **Identifiers:** `RUSTSEC-2026-0427`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Published:** 29 Oct 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by OSV at 29 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `sn-releases` (crates.io): affected `>=0.0.0-0`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The sn-releases crate, all versions, has a path traversal flaw in extract_release_archive: archive entry names are used to build output paths without checking for traversal, so a malicious release archive can write files and create directories outside the destination directory. The source gives few details on how the archive is supplied to the victim. No fix is listed, and the crate is unmaintained, so users should avoid extracting untrusted archives with it.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0427)

## Sources

- [OSV: RUSTSEC-2026-0427](https://osv.dev/vulnerability/RUSTSEC-2026-0427)
- <https://crates.io/crates/sn-releases>
- <https://rustsec.org/advisories/RUSTSEC-2026-0427.html>
- <https://github.com/maidsafe/sn-releases>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/RUSTSEC-2026-0427>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/RUSTSEC-2026-0427/>. Everything for agents: <https://agentprime.io/llms.txt>.