← Back
CVE-2026-42184
high
CVSS 8.8
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**SSRF** (CWE-918) exists in tauri. Attackers reach the vulnerable code path via ``true`` without authentication.
📍 Affected scope
tauri — . Attack surface: `true` / `ping`.
🔥 Severity
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.11.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade tauri to 2.11.1ステージング環境で 2.11.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
tauri
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.11.1"}]}]
crates.io
tauri
[{"type":"SEMVER","events":[{"introduced":"2.0.0"},{"fixed":"2.11.1"}]}]