# CVE-2026-95627: Tauri framework v2 Dialog plugin auto-expands the filesystem scope with attacker-controlled recursion

> Attackers can bypass filesystem scope restrictions in Tauri dialog plugins to gain recursive read/write access to directory trees via XSS.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-j8fp-v6pf-qx45

## What is CVE-2026-95627?

CVE-2026-95627 is a high-severity vulnerability in tauri-plugin-dialog, published on 23 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

When a Tauri application uses the dialog plugin's file or folder picker, an attacker with JavaScript execution (XSS) can force the scope expansion to be recursive, granting read/write access to an entire directory tree after a single user click on a normal-looking OS file dialog. The user has no indication that recursive access was granted, and the expanded scope cannot be revoked for the lifetime of the application.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2026-95627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95627 is a high-severity vulnerability in tauri-plugin-dialog, published on 23 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-95627 in the wild and no public exploit code.

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

## Sources

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

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