Back to CVE records
Medium 5.9Published Sep 23, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects tauri-plugin-updater. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
5.9 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-354
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
JFROG
NVD analysis
Deferred
Record last updated
Sep 23, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Tauri tauri-plugin-updater
tauri:plugin_updater (from the name)
from 2.0.0 before 2.12.0; from 2.12.0
CNA record

References

  • issue-tracking
  • product
  • patch
  • release-notes

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.