Technical impact
The vulnerability exists in react-native-webview 13.7.0 through 17.1.0 when used on Windows, where the WebView2 NewWindowRequested event forwards any requested URI to LaunchUriAsync without validating the scheme or requiring user initiation. Malicious web pages can trigger this behavior using window.open() or target="_blank" links that include schemes such as ms-settings:, causing the application to launch Windows protocol handlers without displaying the normal external‑protocol confirmation dialog. The result is that arbitrary Windows programs or services associated with those URI schemes can be executed as if the user had intentionally launched them.
Affected Systems
The flaw is present only in the react-native-webview library, versions 13.7.0 through 17.1.0, on Windows platforms that utilize WebView2. Any application that embeds this library and loads untrusted or remote web content is vulnerable until it adopts a fixed release. The vulnerability manifests when a user interacts with a malicious or compromised web page within the WebView component; background services are not involved.
Risk and Exploitability
The CVSS score of 5.3 indicates a moderate risk. EPSS data is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting limited public exploitation evidence at present. The attack vector is client‑side: a remote or malicious web page can exploit the internal event handler of the WebView component. The lack of scheme or user‑initiation checks removes the typical external‑protocol confirmation barrier, enabling the attacker to invoke any Windows protocol handler from within the application.