CVE-2026-95625

What it is

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.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of data exposure, data tampering.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-23 09:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-23 19:42 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 5.9 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-09-23 09:17 UTC

Last modified

2026-09-23 19:42 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-354

Record status

Deferred

Attack profile CVSS 3.1 · 5.9

Attack vector

Network

Complexity

High

Privileges needed

High

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-95625.md and follow it. Check whether this project is affected by CVE-2026-95625. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge