CVE-2025-31477

CVE-2025-31477 is a critical-severity improper input validation vulnerability in tauri-plugin-shell (rust), affecting versions < 2.2.1. It is fixed in 2.2.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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.

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

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

Affected versions

tauri-plugin-shell (< 2.2.1) @tauri-apps/plugin-shell (< 2.2.1)

Security releases

tauri-plugin-shell → 2.2.1 (rust) @tauri-apps/plugin-shell → 2.2.1 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

  1. What is CVE-2025-31477? CVE-2025-31477 is a critical-severity improper input validation vulnerability in tauri-plugin-shell (rust), affecting versions < 2.2.1. It is fixed in 2.2.1. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
  2. Which packages are affected by CVE-2025-31477?
    • tauri-plugin-shell (rust) (versions < 2.2.1)
    • @tauri-apps/plugin-shell (npm) (versions < 2.2.1)
  3. Is there a fix for CVE-2025-31477? Yes. CVE-2025-31477 is fixed in 2.2.1. Upgrade to this version or later.
  4. Is CVE-2025-31477 exploitable, and should I be worried? Whether CVE-2025-31477 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2025-31477 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2025-31477?
    • Upgrade tauri-plugin-shell to 2.2.1 or later
    • Upgrade @tauri-apps/plugin-shell to 2.2.1 or later

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo