# CVE-2026-70622: tar-rs 0.4.11 - 0.4.46 Symlink Escape via append_dir_all()

> Attackers can read files outside the intended directory by planting symlinks when a privileged process archives an untrusted directory using tar-rs.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** AZL-95589, AZL-95592, AZL-95604, AZL-95607, AZL-95625, AZL-95628, AZL-95631, AZL-95655, DEBIAN-CVE-2026-70622, GHSA-c2qp-v5vm-7vxf, UBUNTU-CVE-2026-70622

## What is CVE-2026-70622?

CVE-2026-70622 is a high-severity path traversal vulnerability in composefs tar-rs, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

tar-rs versions 0.4.11 through 0.4.46 contain a symlink escape vulnerability in the Builder::append_dir_all() function that allows attackers to read files outside the intended source root directory by planting symlinks in an attacker-controlled directory. When a privileged process archives an untrusted directory, the function follows symlinks without verifying that resolved targets remain within the source root, causing out-of-bounds files to be included in the archive as regular files and disclosed to the attacker.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-70622?


## How do I fix CVE-2026-70622?

Upgrade to a fixed version.

## Is CVE-2026-70622 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70622 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-70622 and fix it if it is affected.

What it is: CVE-2026-70622 is a high-severity path traversal vulnerability in composefs tar-rs, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-70622 exists.

Affected product: composefs tar-rs. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-70622/ (Markdown: https://insights.sbomify.com/CVE-2026-70622/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-70622
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-70622
- OSV: https://osv.dev/vulnerability/CVE-2026-70622

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