CVE-2026-82635
Path-traversal in Pake download_file lets attackers write files and install persistence in user accounts.
Is CVE-2026-82635 being exploited?
Not confirmed. CVE-2026-82635 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-82635?
CVE-2026-82635 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82635?
Yes. A fix has been recorded for CVE-2026-82635. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82635 affect?
CVE-2026-82635 affects Pake < 3.13.1, Desktop apps built from affected Pake trees, macOS/Linux/Windows user accounts. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82635?
Upgrade to Pake v3.13.1, rebuild affected apps, audit for malicious autostart files and block untrusted scripts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-supplied filename allows path traversal to write attacker-controlled files outside ~/Downloads and install autostart persistence, enabling user-level code execution.
Immediate action required
- affected< 3.13.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.