SSRF (Server-Side Request Forgery) in tauri (CVE-2026-42184)
Summary
SSRF in tauri (CVE-2026-42184). Successful exploitation can lead to full system takeover. Exploitable via true. Mitigation: upgrade to 2.11.1 or later.
Original description
The description as published by the source.
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://.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()
};
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42184 has been found in tauri.
Attackers can target a specific entry point like true over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade tauri to 2.11.1 or later.
If unsure, ask your IT team or search "tauri CVE-2026-42184" on the vendor's site.
CVE-2026-42184 (tauri) — CWE-918 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: true / ping
Patched: 2.11.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in tauri. Attackers reach the vulnerable code path via true without authentication.
Check the vendor advisory for the affected versions of tauri. Attack surface: true / ping.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.11.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tauri' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tauri' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tauriを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tauri to 2.11.1ステージング環境で 2.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com