Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
Fixed in tauri-plugin-updater 2.12.0. allowDowngrades was removed from the check command and is now read from the plugin configuration instead, where the frontend cannot reach it, and it defaults to false. An application that provides its own version comparator still takes precedence.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 22 Sep 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Tauri updater plugin's 'check' IPC command accepts an allowDowngrades boolean parameter directly from frontend JavaScript code. When set to true, it replaces the version comparator from "update must be newer" to "update must be different." Because the default permission set grants allow-check to the webview, any XSS in the app frontend can invoke this command and bypass the only anti-rollback protection the updater offers. Combined with another bug, this enables downgrade attacks without even needing to fake a higher version number. | |
| Title | Tauri framework v2 malicious downgrade via allow_downgrades from frontend code | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: JFROG
Published:
Updated: 2026-09-22T17:16:25.195Z
Reserved: 2026-09-22T10:38:03.883Z
Link: CVE-2026-95624
No data.
No data.
No data.
OpenCVE Enrichment
No data.
