GHSA-6mv3-wm7j-h4w5 is a medium-severity (CVSS 6.8) Path Traversal vulnerability in tauri. 1 public exploit reference exists, so weaponization risk is real. A fix is available for tauri — see the affected versions and patch details below.
Tauri Filesystem Scope Glob Pattern is too Permissive
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-6mv3-wm7j-h4w5.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-6mv3-wm7j-h4w5 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
tauri🦀tauri🦀tauri🦀tauriReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The filesystem glob pattern wildcards *, ?, and [...] match file path literals and leading dots by default, which unintentionally exposes sub folder content of allowed paths.
Example: The fs scope $HOME/*.key would also allow $HOME/.ssh/secret.key to be read even though it is in a sub directory of $HOME and is inside a hidden folder.
Scopes without the wildcards are not affected. As ** allows for sub directories the behavior there is also as expected.
Patches
The issue has been patched in the latest release and was backported into the currently supported 1.x branches.
Workarounds
No workaround is known at the time of publication.
References
The original report contained information that the dialog.open component automatically allows one sub directory to be read, regardless of the recursive option.
Imagine a file system looking like
o ../
o documents/
- file.txt
- deeper/
o deep_file.txt
Reproduction steps:
- Trying to load “file.txt” or “deep_file.txt” doesn’t work. Expected
- Select “documents” as folder to open(ie. with window.TAURI.dialog.open)
- Trying to load “file.txt” works. Expected
- Trying to load “deep_file.txt” also works, which isn’t expected
The recursive flag is used in https://github.com/tauri-apps/tauri/blob/cd8c074ae6592303d3f6844a4fb6d262eae913b2/core/tauri/src/scope/fs.rs#L154 to scope the filesystem access to either files in the folder or to also include sub directories.
The original issue was replicated and further investigated.
The root cause was triaged to the glob crate facilitating defaults, which allow the * and [...] to also match path literals.
MatchOptions {
case_sensitive: true,
require_literal_separator: false,
require_literal_leading_dot: false
}
This implicated that not only the dialog.open component was affected but rather all fs scopes containing the * or [...] glob.
During this investigation it became obvious that the current glob matches would also match hidden folder (e.g: .ssh) content by default, without explicitly allowing hidden folders to be matched. This is not commonly expected behavior in comparison to for example bash.
The new default Match options are:
MatchOptions {
case_sensitive: true,
require_literal_separator: true,
require_literal_leading_dot: true
}
Another note security relevant for developers building applications interacting with case sensitive filesystems is, that the
case_sensitiveoption only affects ASCII file paths and is not valid in Unicode based paths. This is considered a known risk until theglobcrate supports non-ASCII file paths for this type of case sensitive matching.
For more Information
If you have any questions or comments about this advisory:
Open an issue in tauri Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | tauri | ≥ 1.0.0&&< 1.0.8 | 1.0.8cargo update -p tauri --precise 1.0.8 |
| 🦀crates.io | tauri | ≥ 1.1.0&&< 1.1.3 | 1.1.3cargo update -p tauri --precise 1.1.3 |
| 🦀crates.io | tauri | ≥ 1.2.0&&< 1.2.3 | 1.2.3cargo update -p tauri --precise 1.2.3 |
| 🦀crates.io | tauri | ≥ 2.0.0-alpha.0&&< 2.0.0-alpha.2 | 2.0.0-alpha.2cargo update -p tauri --precise 2.0.0-alpha.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tauri, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tauri to 1.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6mv3-wm7j-h4w5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6mv3-wm7j-h4w5 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6mv3-wm7j-h4w5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6mv3-wm7j-h4w5 in your dependencies?
O3 Security finds GHSA-6mv3-wm7j-h4w5 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.