CVE-2026-95625

published 23 Sep 2026 · updated 23 Sep 2026

Tauri framework v2 missing updater signature version number validation can be exploited into forced downgrade

5.9MediumCVSS 5.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.12.0.

The Tauri updater plugin verifies update binaries using minisign signatures, but the signature covers only the raw binary bytes. The update manifest -- which contains the version number, download URL, and signature -- is fetched over TLS but is never itself signed or authenticated. Because the only anti-rollback check compares the manifest's version field against the current version, and that field is unsigned, an attacker who can serve a crafted manifest can force installation of any older signed release without possessing the developer's private key.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Tauri=2.12.0, >=2.0.0 <2.12.02.12.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-95625 severity on Zeptric[![CVE-2026-95625](https://zeptric.io/badge/cve/CVE-2026-95625.svg)](https://zeptric.io/cve/CVE-2026-95625)