Tauri's readDir Endpoint Scope can be Bypassed With Symbolic Links

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

EPSS

• CVE-2022-39215: 1.02% estimated exploitation activity in the next 30 days; percentile 63.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 security@tauri.app

Published by the source

16 Sep 2022, 19:28 UTC

Last modified by the source

7 Feb 2023, 21:22 UTC

Source last checked

26 Oct 2026, 15:33 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-28m8-9j7v-x499

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-39215

Advisory: Tauri's readDir Endpoint Scope can be Bypassed With Symbolic Links
IDs: CVE-2022-39215, GHSA-28m8-9j7v-x499
Record: https://patchnext.com/advisories/cve-2022-39215 (revision 1, source checked 26 Oct 2026, 15:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tauri 1.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io tauri: affected < 1.0.6; fixed in 1.0.6

## Suggested inspection (read-only)
- crates.io tauri: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tauri.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-28m8-9j7v-x499 (GitHub-reviewed advisory GHSA-28m8-9j7v-x499 lists affected ranges: crates.io tauri >=0 <1.0.6)

Commands are suggestions: review each one before running it.