CVE-2026-82635: Pake before 3.13.1 joins the JavaScript-supplied filename for the download_file Tauri command onto the user's

Q: How do I fix CVE-2026-82635?

pake: upgrade to 3.13.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-82635 being exploited?

CVE-2026-82635 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-82635 affect?

CVE-2026-82635 affects pake. Severity is high (CVSS 8.8). 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.

This month

HIGH 8.8UPGRADE

CVE-2026-82635 is a high-severity flaw (CVSS 8.8) affecting pake. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 tha

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-22
Published	2026-08-30
Last modified	2026-09-04

Publisher (CNA): JFrog · Vendor: faberon

Last updated 2026-09-04 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-30 13:16 UTCPublished CVE record published
2026-09-04 20:32 UTCUpdated Record last modified

faberon pake UPGRADE

Affected: < 3.13.1

Fixed in: 3.13.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pake || rpm -q pake || pake --version

2. UPGRADE to 3.13.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pake

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pake

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-82635?

pake: upgrade to 3.13.1. Exact commands for each OS are on this page.

Is CVE-2026-82635 being exploited?

CVE-2026-82635 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-82635 affect?

CVE-2026-82635 affects pake. Severity is high (CVSS 8.8). 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.

How urgent is CVE-2026-82635?

Priority 43/100. High severity

References

← Back to latest CVEs