Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

pake vulnerabilities and fixes

Recent CVEs affecting pake, with upgrade or downgrade steps. 1 tracked.

pake has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2026-08-30. Highest priority: CVE-2026-82635 (score 43/100).

FAQ

How do I fix pake vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is pake being exploited right now?

None of the tracked pake CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which pake CVE should I patch first?

CVE-2026-82635 currently ranks highest (43/100): Pake before 3.13.1 joins the JavaScript-supplied filename for the download_file Tauri command onto the user's .

← Back to latest CVEs