https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 05:02:57 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-03884 bdu:2025-03884 https://cve.radiocsirt.org/vuln/bdu:2025-03884 https://cve.radiocsirt.org/vuln/euvd-2026-226811 EUVD-2026-226811 https://cve.radiocsirt.org/vuln/euvd-2026-226811 https://cve.radiocsirt.org/vuln/fkie_cve-2025-31477 <p>The Tauri shell plugin allows access to the system shell. Prior to 2.2.1, the Tauri shell plugin exposes functionality to execute code and open programs on the system. The open endpoint of this plugin is designed to allow open functionality with the system opener (e.g. xdg-open on Linux). This was meant to be restricted to a reasonable number of protocols like https or mailto by default. This default restriction was not functional due to improper validation of the allowed protocols, allowing for potentially dangerous protocols like file://, smb://, or nfs:// and others to be opened by the system registered protocol handler. By passing untrusted user input to the open endpoint these potentially dangerous protocols can be abused to gain remote code execution on the system. This either requires direct exposure of the endpoint to application users or code execution in the frontend of a Tauri application. This vulnerability is fixed in 2.2.1.</p> <p>The Tauri shell plugin allows access to the system shell. Prior to 2.2.1, the Tauri shell plugin exposes functionality to execute code and open programs on the system. The open endpoint of this plugin is designed to allow open functionality with the system opener (e.g. xdg-open on Linux). This was meant to be restricted to a reasonable number of protocols like https or mailto by default. This default restriction was not functional due to improper validation of the allowed protocols, allowing for potentially dangerous protocols like file://, smb://, or nfs:// and others to be opened by the system registered protocol handler. By passing untrusted user input to the open endpoint these potentially dangerous protocols can be abused to gain remote code execution on the system. This either requires direct exposure of the endpoint to application users or code execution in the frontend of a Tauri application. This vulnerability is fixed in 2.2.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-31477 https://cve.radiocsirt.org/vuln/ghsa-c9pr-q8gx-3mgp <p><strong>Affected:</strong> crates.io: tauri-plugin-shell, npm: @tauri-apps/plugin-shell</p> <p>### Impact</p> <p>The Tauri [`shell`](https://tauri.app/plugin/shell/) plugin exposes functionality to execute code and open programs on the system. The [`open`](https://tauri.app/reference/javascript/shell/#open) endpoint of this plugin is designed to allow open functionality with the system opener (e.g. `xdg-open` on Linux). This was meant to be restricted to a reasonable number of protocols like `https` or `mailto` by default.</p> <p>This default restriction was not functional due to improper validation of the allowed protocols, allowing for potentially dangerous protocols like `file://`, `smb://`, or `nfs://` and others to be opened by the system registered protocol handler.</p> <p>By passing untrusted user input to the `open` endpoint these potentially dangerous protocols can be abused to gain remote code execution on the system. This either requires direct exposure of the endpoint to application users or code execution in the frontend of a Tauri application.</p> <p>You are not affected if you have explicitly configured a validation regex or manually set the `open` endpoint to `true` in the plugin configuration.</p> <p>Technically the scope was never a limitation for the rust side as it is not seen as an enforceable security boundary but we decided to mark the rust crate as affected since the plugin does not need to be a frontend dependency to be exposed.</p> <p>### Patches</p> <p>The issue has been patched in the `2.2.1` version of the plugin. The plugin now differentiates between an unset scope and an ex…</p> <p><strong>Affected:</strong> crates.io: tauri-plugin-shell, npm: @tauri-apps/plugin-shell</p> <p>### Impact</p> <p>The Tauri [`shell`](https://tauri.app/plugin/shell/) plugin exposes functionality to execute code and open programs on the system. The [`open`](https://tauri.app/reference/javascript/shell/#open) endpoint of this plugin is designed to allow open functionality with the system opener (e.g. `xdg-open` on Linux). This was meant to be restricted to a reasonable number of protocols like `https` or `mailto` by default.</p> <p>This default restriction was not functional due to improper validation of the allowed protocols, allowing for potentially dangerous protocols like `file://`, `smb://`, or `nfs://` and others to be opened by the system registered protocol handler.</p> <p>By passing untrusted user input to the `open` endpoint these potentially dangerous protocols can be abused to gain remote code execution on the system. This either requires direct exposure of the endpoint to application users or code execution in the frontend of a Tauri application.</p> <p>You are not affected if you have explicitly configured a validation regex or manually set the `open` endpoint to `true` in the plugin configuration.</p> <p>Technically the scope was never a limitation for the rust side as it is not seen as an enforceable security boundary but we decided to mark the rust crate as affected since the plugin does not need to be a frontend dependency to be exposed.</p> <p>### Patches</p> <p>The issue has been patched in the `2.2.1` version of the plugin. The plugin now differentiates between an unset scope and an ex…</p> https://cve.radiocsirt.org/vuln/ghsa-c9pr-q8gx-3mgp