# RUSTSEC-2026-0245: Relative/Absolute Path Traversal (CWE-23/CWE-36) in `decompress_impl` that enables an arbitrary file write.

> A path traversal vulnerability in the sevenz-rust library allows attackers to write arbitrary files via malicious archives, potentially leading to code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Aug 2026

## What is RUSTSEC-2026-0245?

RUSTSEC-2026-0245 is a path traversal vulnerability in sevenz-rust, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

## Summary

All versions of `sevenz-rust` fail to validate file paths when extracting in `decompress_impl` (the underlying function used in the exposed decompress api functions). 

This oversight allows a maliciously crafted archive to extract outside the extraction directory, from both relative paths such as `../../../...` or absolute paths like `C:\\...` or `/etc/...`, which could lead to file disclosure or remote command execution in combination with other flaws or social engineering.

## Details

The following line numbers will be referencing the latest version v0.6.1. The specific point of failure is at `de_funcs.rs::101` inside `decompress_impl`.
``` rust
seven.for_each_entries(|entry, reader| {
    let dest_path = dest.join(entry.name());
    extract_fn(entry, reader, &dest_path)
})?;
```
When the function iterates through each entry, it blindly joins the entry name with the output directory before passing the path into `extract_fn`, `default_entry_extract_fn` unless specified otherwise by user. This allows for relative path traversal from simple path concatenation and absolute path traversal due to [std::path::join](https://doc.rust-lang.org/std/path/struct.Path.html#method.join)'s edge case where if the "[passed] path is absolute, it replaces the current path."

`default_entry_extract_fn` also fails to validate if the entry it is given has a safe extraction path before it writes to disk at `de_funcs.rs::135`.  

## Status

The project has been abandoned and the repository has been deleted, so no upstream fix is expected. Users should migrate away from the library in favor of a modern up-to-date 7z library such as `sevenz-rust2`.

## Which versions are affected by RUSTSEC-2026-0245?

1 open source package ship an affected version, including sevenz-rust.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sevenz-rust` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2026-0245?

No fix has been published for RUSTSEC-2026-0245 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2026-0245 being exploited?

There is no known exploitation of RUSTSEC-2026-0245 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0245 and fix it if it is affected.

What it is: RUSTSEC-2026-0245 is a path traversal vulnerability in sevenz-rust, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of RUSTSEC-2026-0245 in the wild and no public exploit code.

Affected packages and fixed versions:
- sevenz-rust (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0245/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0245/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0245

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0245/
Summaries are generated and may contain mistakes; the official description above is the record.