Vulnerability · Published Sep 23, 2026 · Assigned by JFROG

CVE-2026-95625Tauri framework v2 missing updater signature version number validation can be exploited into forced downgrade

Medium 5.9

In plain English

A medium-severity security flaw in tauri-plugin-updater from Tauri. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities).

Severity (CVSS 3.1)5.9Medium

Exploit odds (30 days)0.2%top 95.2% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

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 packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
Ubuntu:24.04:LTS	minisign	no fix listed	UBUNTU-CVE-2026-95625
Ubuntu:26.04:LTS	minisign	no fix listed	UBUNTU-CVE-2026-95625
Ubuntu:26.10	minisign	no fix listed	UBUNTU-CVE-2026-95625

Affected products (as reported)

Vendor	Product	Versions
Tauri	tauri-plugin-updater	2.0.0 – before 2.12.02.12.0 – through *

Weakness: CWE-354 · Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

References

GHSA-j38x-g3m3-95fr (tauri-apps/plugins-workspace) issue-tracking
tauri-apps/plugins-workspace repository product
Add requireSignedVersion to bind an update to its signed version patch
tauri-plugin-updater 2.12.0 release notes release-notes