# CVE-2026-95626: Tauri framework v2 CSP nonce protection bypass via data and blob URI schemes allows an XSS to RCE chains

> Attackers can bypass CSP nonce protections in Tauri apps using data or blob URIs to execute arbitrary scripts, potentially leading to remote code execution.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-757j-xrg3-9g6p

## What is CVE-2026-95626?

CVE-2026-95626 is a high-severity cross-site scripting vulnerability in tauri, published on 23 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

Tauri's Content Security Policy hardening, which injects a random nonce to restrict script execution, provides zero protection when an application includes data: or blob: in its script-src directive. Per the CSP Level 3 specification, these scheme sources remain active even when a nonce is present, allowing arbitrary script execution without knowing the nonce.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-95626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95626 is a high-severity cross-site scripting vulnerability in tauri, published on 23 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-95626 in the wild and no public exploit code.

Affected product: tauri. 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-95626/ (Markdown: https://insights.sbomify.com/CVE-2026-95626/index.md)
```

## Sources

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

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