GHSA-7gmj-67g7-phm9 CVE-2026-42184
Tauri has an Origin Confusion Issue that Allows Remote Pages to Invoke Local-Only IPC Commands
- Severity
- 0.0 / 10
- High · CVSS 4.0
- Exploit chance (EPSS)
- 0.31%
- Chance of exploitation in the next 30 days. Higher than 24.09% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-918 Server-Side Request Forgery (SSRF)
- Fix
2.11.1- Upgrade tauri to this version or later
Description
Summary
A flaw in Tauri's is_local_url() 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., includinghttp://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:
#[cfg(any(windows, target_os = "android"))]
let local = {
let protocol_url = self.manager().tauri_protocol_url(uses_https);
let maybe_protocol = current_url
.domain()
.and_then(|d| d.split_once('.')) // BUG: only splits on first dot
.unwrap_or_default()
.0;
protocols.contains_key(maybe_protocol) && scheme == protocol_url.scheme()
};
split_once('.') 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.contains_key("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, is_local_url() classifies it as a local origin and the command succeeds.
capabilities/main.json contains the following code, which only exposes ping locally:
{
"$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:
tauri::Builder::default()
.register_uri_scheme_protocol("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.
Affected versions
crates.io
| Package | Vulnerable | Fixed in |
|---|---|---|
| tauri | >= 2.0.0, < 2.11.1 |
2.11.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
tauri crates.io → 2.11.1
- cargo
cargo update -p tauri --precise 2.11.1
Severity breakdown
CVSS 4.0 0.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
- Attack vector
- Network
- Attack complexity
- High
- Attack requirements
- Present
- Privileges required
- None
- User interaction
- Passive
- Confidentiality (vulnerable system)
- Low
- Integrity (vulnerable system)
- High
- Availability (vulnerable system)
- Low
- Confidentiality (subsequent systems)
- None
- Integrity (subsequent systems)
- None
- Availability (subsequent systems)
- None
CVSS 3.1 8.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-918: Server-Side Request Forgery (SSRF)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-57fm-592m-34r7 iFrames Bypass Origin Checks for Tauri API Access Control | Medium | Also affects tauri |
| GHSA-wmff-grcw-jcfm Tauri vulnerable to Regression on Filesystem Scope Checks for Dotfiles | Critical | Also affects tauri |
| GHSA-4wm2-cwcf-wwvp Tauri Open Redirect Vulnerability Possibly Exposes IPC to External Sites | Medium | Also affects tauri |
| GHSA-6mv3-wm7j-h4w5 Tauri Filesystem Scope Glob Pattern is too Permissive | High | Also affects tauri |
| GHSA-q9wv-22m9-vhqh Tauri Filesystem Scope can be Partially Bypassed | Medium | Also affects tauri |
| GHSA-28m8-9j7v-x499 Tauri's readDir Endpoint Scope can be Bypassed With Symbolic Links | Medium | Also affects tauri |
| EEF-CVE-2026-115700 SSRF allowlist bypass via percent-encoded bracketed IPv6 or trailing-dot IP literal in hackney | Not rated yet | Same weakness, CWE-918 |
| GHSA-2wqp-q3c6-ccj5 MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints | Medium | Same weakness, CWE-918 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor