RUSTSEC-2026-0427
Vulnerability from osv_rustsec – Published: 2026-10-29 12:00 – Updated: 2026-10-30 11:12 – Source websiteSafeReleaseRepoActions::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):
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.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"categories": [
"code-execution"
],
"cvss": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [
"sn_releases::SafeReleaseRepoActions::extract_release_archive"
],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "sn-releases",
"purl": "pkg:cargo/sn-releases"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [],
"database_specific": {
"license": "CC0-1.0"
},
"details": "`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).\n\nIn `src/lib.rs` (`extract_release_archive`, zip branch):\n\n```rust\nlet mut file = archive.by_index(i)?;\nlet out_path = dest_dir_path.join(file.name()); // file.name() is the raw entry name\nif file.name().ends_with(\u0027/\u0027) {\n std::fs::create_dir_all(\u0026out_path)?; // no `..` check\n} else {\n let mut outfile = std::fs::File::create(\u0026out_path)?; // writes outside dest\n std::io::copy(\u0026mut file, \u0026mut outfile)?;\n}\n```\n\nThe crate is unmaintained (latest release 0.3.1, 2024-10-22) and no fixed version is available.",
"id": "RUSTSEC-2026-0427",
"modified": "2026-10-30T11:12:39Z",
"published": "2026-10-29T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/sn-releases"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0427.html"
},
{
"type": "WEB",
"url": "https://github.com/maidsafe/sn-releases"
}
],
"related": [],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "`sn-releases`: `extract_release_archive` writes archive entries without a path-traversal check (zip-slip)"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.