tauri-plugin-shell

Version	Released
`3.0.0-alpha.0` pre	Sep 13, 2026
`2.3.6` patch	Aug 31, 2026
`2.3.5` unknown	Feb 03, 2026
`2.3.4` unknown	Jan 08, 2026
`2.3.3` unknown	Oct 27, 2025
`2.3.2` unknown	Oct 26, 2025
`2.3.1` unknown	Aug 25, 2025
`2.3.0` unknown	Jun 25, 2025
`2.2.2` unknown	Jun 16, 2025
`2.2.1` unknown	Apr 02, 2025
`2.2.0` unknown 1 CVE	Dec 09, 2024
`2.0.2` unknown 1 CVE	Oct 20, 2024
`2.0.1` unknown 1 CVE	Oct 03, 2024
`2.0.0` unknown 1 CVE	Oct 02, 2024
`2.0.0-rc.4` unknown 1 CVE	Oct 02, 2024
`2.0.0-rc.3` unknown 1 CVE	Aug 29, 2024
`2.0.0-rc.2` unknown 1 CVE	Aug 20, 2024
`2.0.0-rc.1` unknown 1 CVE	Aug 17, 2024
`2.0.0-rc.0` unknown 1 CVE	Aug 02, 2024
`2.0.0-beta.10` unknown 1 CVE	Jul 31, 2024
`2.0.0-beta.9` unknown 1 CVE	Jul 12, 2024
`2.0.0-beta.8` unknown 1 CVE	Jul 02, 2024
`2.0.0-beta.7` unknown 1 CVE	May 30, 2024
`2.0.0-beta.6` unknown 1 CVE	May 30, 2024
`2.0.0-beta.5` unknown 1 CVE	May 11, 2024
`2.0.0-beta.4` unknown 1 CVE	May 01, 2024
`2.0.0-beta.3` unknown 1 CVE	Mar 21, 2024
`2.0.0-beta.2` unknown 1 CVE	Mar 07, 2024
`2.0.0-beta.1` unknown 1 CVE	Feb 21, 2024
`2.0.0-beta.0` unknown 1 CVE	Feb 03, 2024
`2.0.0-alpha.6` unknown 1 CVE	Dec 20, 2023
`2.0.0-alpha.5` unknown 1 CVE	Dec 14, 2023
`2.0.0-alpha.4` unknown 1 CVE	Oct 29, 2023
`2.0.0-alpha.3` unknown 1 CVE	Oct 23, 2023
`2.0.0-alpha.2` unknown 1 CVE	Sep 07, 2023
`2.0.0-alpha.1` unknown 1 CVE	Aug 14, 2023
`2.0.0-alpha.0` unknown 1 CVE	May 24, 2023

3.0.0-alpha.0 pre

Sep 13, 2026

2.3.6 patch

Aug 31, 2026

2.3.5 unknown

Feb 03, 2026

2.3.4 unknown

Jan 08, 2026

2.3.3 unknown

Oct 27, 2025

2.3.2 unknown

Oct 26, 2025

2.3.1 unknown

Aug 25, 2025

2.3.0 unknown

Jun 25, 2025

2.2.2 unknown

Jun 16, 2025

2.2.1 unknown

Apr 02, 2025

2.2.0 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Dec 09, 2024

2.0.2 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Oct 20, 2024

2.0.1 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Oct 03, 2024

2.0.0 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Oct 02, 2024

2.0.0-rc.4 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Oct 02, 2024

2.0.0-rc.3 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Aug 29, 2024

2.0.0-rc.2 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Aug 20, 2024

2.0.0-rc.1 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Aug 17, 2024

2.0.0-rc.0 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Aug 02, 2024

2.0.0-beta.10 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Jul 31, 2024

2.0.0-beta.9 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Jul 12, 2024

2.0.0-beta.8 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Jul 02, 2024

2.0.0-beta.7 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

May 30, 2024

2.0.0-beta.6 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

May 30, 2024

2.0.0-beta.5 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

May 11, 2024

2.0.0-beta.4 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

May 01, 2024

2.0.0-beta.3 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Mar 21, 2024

2.0.0-beta.2 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Mar 07, 2024

2.0.0-beta.1 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Feb 21, 2024

2.0.0-beta.0 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Feb 03, 2024

2.0.0-alpha.6 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Dec 20, 2023

2.0.0-alpha.5 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Dec 14, 2023

2.0.0-alpha.4 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Oct 29, 2023

2.0.0-alpha.3 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Oct 23, 2023

2.0.0-alpha.2 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Sep 07, 2023

2.0.0-alpha.1 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

Aug 14, 2023

2.0.0-alpha.0 unknown

1 CVE

CVE-2025-31477 GHSA-c9pr-q8gx-3mgp Apr 02, 2025

Improper Scope Validation in the `open` Endpoint of `tauri-plugin-shell`

Critical

Network Low None None

Impact

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.

You are not affected if you have explicitly configured a validation regex or manually set the open endpoint to true in the plugin configuration.

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.

Patches

The issue has been patched in the 2.2.1 version of the plugin. The plugin now differentiates between an unset scope and an explicit validation disable for the open endpoint.

Workarounds

A way to prevent arbitrary protocols would be setting the shell plugin configuration value open to true.

tauri.conf.json

"plugins": {
    "shell": {
          "open": true
     },
}

The above will only allow mailto, http and https links to be opened.

If the open endpoint should not be allowed at all there are two possible workarounds.

Defining a non matching regex like tauri^ in the plugin configuration
Removing shell:default and all instances of shell:allow-open from the capabilities

Alternatively we recommend usage of the opener plugin, as the shell plugin deprecated the open endpoint previously.

References

PoC

This is a windows specific proof of concept.

Use create-tauri-app to make a new Tauri app.
Run tauri add shell to add the shell plugin.
Execute await window.__TAURI_INTERNALS__.invoke("plugin:shell|open", {path: "file:///c:/windows/system32/calc.exe"}); in the developer console.
Observe the calculator being executed

Fixed in


          2.2.1

References

Updated Sep 10, 2026 · Source: OSV.dev

May 24, 2023

Activity

Reach

Details