Skip to content
Fencer Intel
medium 6.8

CVE-2022-46171 json

Tauri vulnerable to path traversal

published 3y ago modified 4mo ago also GHSA-6mv3-wm7j-h4w5 , EUVD-2022-7536

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 65%
public exploits
0
none known

Summary

Tauri is a framework for building binaries for all major desktop platforms. The filesystem glob pattern wildcards `*`, `?`, and `[...]` match file path literals and leading dots by default, which unintentionally exposes sub folder content of allowed paths. Scopes without the wildcards are not affected. As `**` allows for sub directories the behavior there is also as expected. The issue has been patched in the latest release and was backported into the currently supported 1.x branches. There are no known workarounds at the time of publication.

Patch / fix

  • crates.io tauri 1.0.8, 1.1.3, 1.2.3, 2.0.0-alpha.2
  • tauri tauri 1.0.8, 1.1.3, 1.2.3

Is CVE-2022-46171 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

1.07% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/tauri-apps/tauri/security/advisories/GHSA-6mv3-wm7j-h4w5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 6.8 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
crates.io tauri
>=1.0.0, <1.0.8
>=1.1.0, <1.1.3
>=1.2.0, <1.2.3
>=2.0.0-alpha.0, <2.0.0-alpha.2
1.0.8
1.1.3
1.2.3
2.0.0-alpha.2

Affected products

  • tauri-apps tauri

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.