CVE-2026-42184: Tauri: Origin Confusion Allows Remote Pages to Invoke Local-Only IPC Commands

Published May 6, 2026
·
Updated

Summary A flaw in Tauri's islocalurl() function causes it to incorrectly classify remote URLs as trusted local origins on Windows and Android. On these systems, Tauri maps custom URI scheme protocols to http://<scheme>.localhost/ because those platforms' WebView implementations cannot serve custom URI schemes directly.

The issue is that Tauri's check to see if the origin is local, only checks the first subdomain of the URL. An attacker can abuse this by hosting a page on a domain whose subdomain matches the custom scheme of the application (e.g. http://app.attacker.com/)."

Example: - Local URL: app://localhost/ → on Android/Windows: http://app.localhost/ - The check passes for any URL starting with http://app., including http://app.evil.com/

As a result, the attacker page can invoke backend commands that the developer intended to be accessible only to the app's own frontend and that are explicitly restricted from being called by external or remote origins.

Details Vulnerable function:

rust #[cfg(any(windows, targetos = "android"))] let local = { let protocolurl = self.manager().tauriprotocolurl(useshttps); let maybeprotocol = currenturl .domain() .andthen(|d| d.splitonce('.')) // BUG: only splits on first dot .unwrapordefault() .0;

protocols.containskey(maybeprotocol) && scheme == protocolurl.scheme() };

Link: https://github.com/tauri-apps/tauri/blob/1ef6a119b1571d1da0acc08bdb7fd5521a4c6d52/crates/tauri/src/webview/mod.rs#L1680

splitonce('.') discards everything after the first .. For http://app.evil.com/, the extracted label is app. If the application has registered a protocol named app, protocols.containskey("app") returns true and the URL is classified as Origin::Local. The correct check must assert the full domain is exactly <protocol>.localhost.

PoC We created a proof of concept app that can be found here. The app registers a custom app:// protocol and exposes a ping command restricted to local origins only. It provides a button to open a URL in a WebView, pre-filled with https://app.robbe-bc9.workers.dev/, an attacker-controlled page that invokes ping on load. Because the domain's first label matches the registered app protocol, islocalurl() classifies it as a local origin and the command succeeds.

capabilities/main.json contains the following code, which only exposes ping locally:

json { "$schema": "../../../crates/tauri-schema-generator/schemas/capability.schema.json", "identifier": "main", "local": true, "windows": [""], "permissions": [ "sample:allow-ping" ] }

src/lib.rs contains the following code, to register a custom scheme:

rust tauri::Builder::default() .registerurischemeprotocol("app", |ctx, request| { ... })

Impact The attacker page can invoke backend commands that the developer intended to be accessible only to the app's own frontend and that are explicitly restricted from being called by external or remote origins.

Other sources

Tauri is a framework for building binaries for all major desktop platforms. From 2.0 to 2.11.0, a flaw in Tauri's islocalurl() function causes it to incorrectly classify remote URLs as trusted local origins on Windows and Android. On these systems, Tauri maps custom URI scheme protocols to http://<scheme>.localhost/ because those platforms' WebView implementations cannot serve custom URI schemes directly. The issue is that Tauri's check to see if the origin is local, only checks the first subdomain of the URL. An attacker can abuse this by hosting a page on a domain whose subdomain matches the custom scheme of the application. This vulnerability is fixed in 2.10.3.

MITRE

Affected Software

2 affected componentsFixes available
rust/tauri>=2.0.0<=2.11.0
2.11.1
Tauri Tauri>=2.0.0<2.10.3

Event History

May 6, 2026
Advisory Published
via GitHub·04:58 PM
Data Sourced
via GitHub·04:58 PM
DescriptionWeaknessAffected Software
May 27, 2026
CVE Published
via MITRE·02:29 PM
Data Sourced
via MITRE·02:29 PM
DescriptionWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-42184?

CVE-2026-42184 has been classified as a moderate severity vulnerability due to its potential to classify remote URLs as trusted origins.

2

How do I fix CVE-2026-42184?

To fix CVE-2026-42184, upgrade the Tauri package to version 2.11.1 or later.

3

What systems are affected by CVE-2026-42184?

CVE-2026-42184 specifically affects Windows and Android platforms using the Tauri framework.

4

What component is vulnerable in CVE-2026-42184?

The vulnerability lies in the `is_local_url()` function of Tauri which misclassifies remote URLs.

5

Can CVE-2026-42184 lead to further security issues?

Yes, CVE-2026-42184 can expose applications to security risks by allowing unauthorized access to potentially malicious remote URLs.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203