Tauri vulnerable to Regression on Filesystem Scope Checks for Dotfiles

Exploitation

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

CVSS

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

EPSS

• CVE-2023-34460: 0.65% estimated exploitation activity in the next 30 days; percentile 51.09 (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 The 1.4.0 release includes a regression on the filesystem scope check for dotfiles on Linux and macOS. Previously dotfiles (eg. $HOME/.ssh/) were not implicitly allowed by the glob wildcard scopes (eg. $HOME/), but a regression was introduced when a configuration option for this behavior was implemented and dotfiles were implicitly allowed. Only Tauri applications using wildcard scopes in the fs endpoint are affected. Only macOS and Linux systems are affected. Patches The regression has been patched on v1.4.1. Workarounds There are no known workarounds at this time, users should update to v1.4.1 immediately. References See the original advisory for more information. For more Information 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

21 Jun 2023, 18:35 UTC

Last modified by the source

7 Nov 2023, 05:02 UTC

Source last checked

26 Oct 2026, 15:37 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wmff-grcw-jcfm

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

# Patch Next advisory brief: CVE-2023-34460

Advisory: Tauri vulnerable to Regression on Filesystem Scope Checks for Dotfiles
IDs: CVE-2023-34460, GHSA-wmff-grcw-jcfm
Record: https://patchnext.com/advisories/cve-2023-34460 (revision 1, source checked 26 Oct 2026, 15:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.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.4.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io tauri: affected >= 1.4.0, <= 1.4.0; fixed in 1.4.1

## 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-wmff-grcw-jcfm (GitHub-reviewed advisory GHSA-wmff-grcw-jcfm lists affected ranges: crates.io tauri >=1.4.0 <=1.4.0)

Commands are suggestions: review each one before running it.