# CVE-2026-95624: Tauri framework v2 malicious downgrade via allow_downgrades from frontend code

> Attackers can bypass updater anti-rollback protections via frontend code, enabling downgrade attacks that may lead to code execution.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-rjc6-5hfg-grp9, GHSA-wqjv-7vqv-x3mj

## What is CVE-2026-95624?

CVE-2026-95624 is a medium-severity vulnerability in tauri-plugin-updater, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Tauri updater plugin's 'check' IPC command accepts an allowDowngrades boolean parameter directly from frontend JavaScript code. When set to true, it replaces the version comparator from "update must be newer" to "update must be different." Because the default permission set grants allow-check to the webview, any XSS in the app frontend can invoke this command and bypass the only anti-rollback protection the updater offers. Combined with another bug, this enables downgrade attacks without even needing to fake a higher version number.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-95624 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95624 is a medium-severity vulnerability in tauri-plugin-updater, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-95624 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-95624/ (Markdown: https://insights.sbomify.com/CVE-2026-95624/index.md)
```

## Sources

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

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