CVE-2022-41874 is a low-severity (CVSS 2.6) CWE-668 vulnerability in Tauri. A fix is available for Tauri — see the affected versions and patch details below.
Tauri Filesystem Scope can be Partially Bypassed
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-41874.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
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
Due to incorrect escaping of special characters in paths selected via the file dialog and drag and drop functionality, it was possible to partially bypass the fs scope definition. It was not possible to traverse into arbitrary paths, as the issue was limited to neighboring files and sub folders of already allowed paths.
The impact differs on Windows, MacOS and Linux due to different specifications of valid path characters.
On Linux or MacOS based systems it was possible to use the *, ** and [a-Z] patterns inside a path, which allowed to read the content of sub directories and single character files in a folder, where only specific files or the directory itself were allowed.
On Windows [a-Z] was the possible bypass pattern, as * is not treated as a valid path component. This implies that only single character files inside an already allowed directory were unintentionally accessible.
This bypass depends on the file picker dialog or dragged files, as user selected paths are automatically added to the allow list at runtime.
A successful bypass requires the user to select a pre-existing malicious file or directory during the file picker dialog and an adversary controlled logic to access these files. This means the issue by itself can not be abused and requires further intentional or unintentional privileges.
Workaround
Disable the dialog and fileDropEnabled component inside the tauri.conf.json.
Patches
The issue has been resolved in #5237 and the implementation now properly escapes the special characters. The patch has been included in releases: 1.0.7, 1.1.2 and 1.2.0
For more information
This issue was initially reported by MessyComposer in #5234.
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.7 | 1.0.7cargo update -p Tauri --precise 1.0.7 |
| 🦀crates.io | Tauri | ≥ 1.1.0&&< 1.1.2 | 1.1.2cargo update -p Tauri --precise 1.1.2 |
Affected Products
tauritauriDetection & 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.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41874 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.
Frequently Asked Questions
Is CVE-2022-41874 in your dependencies?
Find it across crates.io, including transitive dependencies.