Cyber Resilience

CVE-2025-31477

CriticalPublic PoC

Published: 02 April 2025

Published
02 April 2025
Modified
29 April 2025
KEV Added
Patch
CVSS Score v4 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0240 85.4th percentile
Risk Priority 20 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2025-31477 is a critical-severity Improper Input Validation (CWE-20) vulnerability in Tauri Plugin-Shell. Its CVSS base score is 9.3 (Critical).

Operationally, ranked in the top 14.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis

The Tauri shell plugin prior to version 2.2.1 contains an input validation flaw in its open endpoint. The endpoint is intended to invoke the system opener only for a restricted set of safe protocols such as https or mailto, but the allow-list check is ineffective, permitting arbitrary protocols including file://, smb://, and nfs:// to reach the registered OS handler.

An attacker who can supply untrusted input to the open function—either through direct network exposure of the endpoint or by achieving JavaScript execution inside a Tauri frontend—can therefore launch arbitrary local resources or remote shares. Successful abuse yields remote code execution on the host with the privileges of the Tauri application.

The issue is resolved in plugin release 2.2.1; the referenced commit and GitHub Security Advisory GHSA-c9pr-q8gx-3mgp document the corrected protocol validation logic and recommend immediate upgrade for all affected applications.

EPSS rose from a low baseline to a peak of 0.0510 on 2026-05-12 before receding, indicating measurable post-disclosure exploitation interest.

EU & UK References

Vulnerability details

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…

more

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.

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

tauri
plugin-shell
≤ 2.2.1 · ≤ 2.2.1

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-20

Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.

addresses: CWE-20

Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.

addresses: CWE-20

Directly implements checks on information inputs to reject invalid data before processing.

addresses: CWE-20

Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.

References