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

> Attackers can force installation of older, vulnerable application versions by serving unsigned update manifests, bypassing anti-rollback protections in the Tauri updater.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-j38x-g3m3-95fr, GHSA-p8c6-29q6-cqw7, UBUNTU-CVE-2026-95625

## What is CVE-2026-95625?

CVE-2026-95625 is a medium-severity vulnerability in tauri-plugin-updater, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### 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.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2026-95625?


## How do I fix CVE-2026-95625?

No fix has been published for CVE-2026-95625 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-95625 being exploited?

There is no known exploitation of CVE-2026-95625 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95625 and fix it if it is affected.

What it is: CVE-2026-95625 is a medium-severity vulnerability in tauri-plugin-updater, published on 23 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-95625 in the wild and no public exploit code.

Affected product: tauri-plugin-updater. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95625/ (Markdown: https://insights.sbomify.com/CVE-2026-95625/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95625
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95625
- OSV: https://osv.dev/vulnerability/CVE-2026-95625

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95625/
Summaries are generated and may contain mistakes; the official description above is the record.