How severe is CVE-2022-39215?

CVE-2022-39215 has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-39215?

CVE-2022-39215 affects the following packages: tauri (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2022-39215?

Update tauri to 1.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39215 is resolved across your whole dependency graph.

How do I detect CVE-2022-39215 in my crates.io dependencies?

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.

How do I mitigate CVE-2022-39215 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2022-39215 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-39215, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-39215?

CVE-2022-39215 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-39215?

CVE-2022-39215 is classified as Path Traversal (CWE-22), CWE-59 (CWE-59). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-39215 published, and has it been updated?

CVE-2022-39215 was published on September 15, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

HIGH severity

CVE-2022-39215 — tauri

HIGHFix: tauri-apps/tauri#5123

CVE-2022-39215 is a high-severity (CVSS 8.3) Path Traversal vulnerability in tauri. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for tauri — see the affected versions and patch details below.

The readDir Endpoint Scope can be Bypassed With Symbolic Links in Tauri

Also known asGHSA-28m8-9j7v-x499RUSTSEC-2022-0088

Published

Sep 15, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-39215.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

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

1 pkg affected

🦀tauri

Real-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 missing canonicalization when readDir is called recursively, it was possible to display directory listings outside of the defined fs scope. This required a crafted symbolic link or junction folder inside an allowed path of the fs scope. No arbitrary file content could be leaked.

Patches

The issue has been resolved in https://github.com/tauri-apps/tauri/pull/5123 and the implementation now properly checks if the requested (sub) directory is a symbolic link outside of the defined scope.

Workarounds

Disable the readDir endpoint in the allowlist inside the tauri.conf.json.

For more information

This issue was initially reported by martin-ocasek in #4882.

If you have any questions or comments about this advisory:

Open an issue in tauri
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`tauri`	all versions	1.0.6`cargo update -p tauri --precise 1.0.6`

Affected Products

1 product · 1 configurations

Application

tauritauri

< 1.0.6

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Tauri is a framework for building binaries for all major desktop platfor…

github.comNVDSep 2022

Detection & mitigation playbook

Open-source dependency

Detect
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.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39215 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact Due to missing canonicalization when `readDir` is called recursively, it was possible to display directory listings outside of the defined `fs` scope. This required a crafted symbolic link or junction folder inside an allowed path of the `fs` scope. No arbitrary file content could be leaked. ### Patches The issue has been resolved in https://github.com/tauri-apps/tauri/pull/5123 and the implementation now properly checks if the requested (sub) directory is a symbolic link outside of the defined `scope`. ### Workarounds Disable the `readDir` endpoint in the `allowlist` inside the