Skip to main content
CVE-2026-130628VulnerabilityPublished

react-native-webview 13.7.0 through 17.1.0 on Windows contains an unrestricted URI scheme launch vulnerability in the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130628· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 17 Nov 2026, 16:51 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.3
CNA (VulnCheck)CVSS 3.14.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
react-native-webviewreact-native-webviewAffected
  • >=13.7.0 <=17.1.0
Fixed in–
npmreact-native-webviewpkg:npm/react-native-webviewOther threatsAffected
  • >=13.7.0 <=17.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should exercise caution when loading untrusted web content in react-native-webview on Windows. Consider implementing additional application-level controls to restrict or monitor URI scheme launches.

Description

A vulnerability exists in react-native-webview versions 13.7.0 through 17.1.0 on Windows where the WebView2 component's new window request handler allows launching URIs with unrestricted schemes. This occurs because the handler passes requested URIs to LaunchUriAsync without verifying the URI scheme or requiring user initiation. Consequently, malicious web content can open new windows or links using schemes like ms-settings: to invoke Windows protocol handlers without triggering the usual external-protocol confirmation prompt.

References

Community reviews

Loading reviews…