# CVE-2026-82635: Pake arbitrary file write via unsanitized download_file filename

> Attackers can write arbitrary files outside the Downloads directory via unsanitized filenames, enabling persistence and code execution in user accounts.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-9r73-w272-42v3

## What is CVE-2026-82635?

CVE-2026-82635 is a high-severity path traversal vulnerability in tw93 Pake, published on 30 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

Pake before 3.13.1 joins the JavaScript-supplied filename for the download_file Tauri command onto the user's Downloads directory with no sanitization. A filename containing path traversal sequences (for example ../Library/LaunchAgents/com.evil.plist) or an absolute path resolves outside ~/Downloads. The command then fetches attacker-controlled content from the supplied URL (via Rust HTTP, not the browser) and writes it to that path. A script that can invoke the command can overwrite user-writable files and install persistence (macOS LaunchAgents, Linux autostart, Windows Startup), leading to code execution in the user account. All desktop apps generated from an affected Pake tree expose the same command.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Faberon Pake.

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

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

## Is CVE-2026-82635 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82635 is a high-severity path traversal vulnerability in tw93 Pake, published on 30 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 CVE-2026-82635 in the wild and no public exploit code.

Affected product: tw93 Pake. 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-82635/ (Markdown: https://insights.sbomify.com/CVE-2026-82635/index.md)
```

## Sources

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

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