CVE-2026-95623: Improper SSRF Protection via HTTP Redirects in tauri-plugin-http
The Tauri HTTP plugin validates requested URLs against the application's configured scope allowlist only once, on the initial request. When the remote server responds with an HTTP 3xx redirect, reqwest follows the redirect internally without re-checking the new target URL against the scope. This allows an attacker who controls an allowed URL (or finds an open redirect on an allowed host) to reach disallowed destinations such as cloud metadata endpoints, localhost services, or internal network hosts.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
tauri-plugin-httpto a version that resolves this vulnerability.Fixed in 2.7.0 - Configuration
Enable scopeRedirects in the HTTP plugin configuration: {"plugins":{"http":{"scopeRedirects":true}}}.
tauri-plugin-http scopeRedirects = true
Event History
Frequently Asked Questions
What conditions are required for exploitation?
The attacker must be able to cause a request to an allowed URL that they control, or use an open redirect on an allowed host. The redirect must then point to a destination outside the configured scope allowlist.
Which applications are most exposed?
Applications that use tauri-plugin-http and allowlist externally controlled URLs or hosts with open redirects are most exposed. The issue can be used to reach disallowed destinations including cloud metadata endpoints, localhost services, and internal network hosts.