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

Published Sep 23, 2026
·
Updated

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 Software

1 affected component
Tauri Tauri updater plugin=2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade tauri-plugin-updater to a version that resolves this vulnerability.

    Fixed in 2.12.0
  2. Configuration

    Enable the requireSignedVersion option so the endpoint-announced version is compared against the version in the signature's trusted comment.

    tauri-plugin-updater requireSignedVersion = true

Event History

Sep 23, 2026
CVE Published
via MITRE·08:51 AM
Data Sourced
via MITRE·08:51 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·09:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What access does an attacker need to force a downgrade?

The attacker must be able to serve a crafted update manifest to the application. They do not need the developer's private signing key, because they can reference an older release that already has a valid minisign signature.

2

Can an attacker install an arbitrary modified binary through this issue?

The available information describes forced installation of an older signed release. The updater still verifies the signature over the binary bytes, so the attacker relies on an existing validly signed binary rather than creating a newly signed one.

3

Which update data can be manipulated to bypass rollback protection?

The manifest's version number is used for the anti-rollback comparison, but it is not covered by the binary signature. The manifest also contains the download URL and signature and is fetched over TLS without being independently signed or authenticated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203