cve.bz

CVE-2022-46171 tauri tauri: Path traversal

7.7 highExploit referenceEPSS 1.1%Fix available

High (7.7) in tauri tauri. EPSS 1.1% estimated probability of exploitation activity in the next 30 days. Fixed in tauri 1.0.8, 1.1.3, 1.2.3.

On this page
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.

Severity

CVSS 3.1

7.7 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 66th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2025-04-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-46171 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-46171?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-46171?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-46171 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
tauri:taurifrom 1.0.0 before 1.0.8
tauri:taurifrom 1.1.0 before 1.1.3
tauri:taurifrom 1.2.0 before 1.2.3
tauri:tauri2.0.0:alpha0
tauri:tauri2.0.0:alpha1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6mv3-wm7j-h4w5crates.iotauri>=1.0.0 <1.0.81.0.8
GHSA-6mv3-wm7j-h4w5crates.iotauri>=1.1.0 <1.1.31.1.3
GHSA-6mv3-wm7j-h4w5crates.iotauri>=1.2.0 <1.2.31.2.3
GHSA-6mv3-wm7j-h4w5crates.iotauri>=2.0.0-alpha.0 <2.0.0-alpha.22.0.0-alpha.2

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON