Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
Upgrade to tauri-plugin-http 2.7.0 or later and turn on the new scopeRedirects option. Both steps are needed. The fix is opt-in, so 2.7.0 on its own still follows a redirect out of scope; the option is what makes the plugin check every hop. Tauri made it opt-in because a redirect that leaves the scope now fails, which changes behaviour for apps that were relying on it. {"plugins": {"http": {"scopeRedirects": true}}} Nothing in the 2.0.0 to 2.6.1 range has a fix available.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 22 Sep 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 22 Sep 2026 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Improper SSRF Protection via HTTP Redirects in tauri-plugin-http | |
| Weaknesses | CWE-918 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: JFROG
Published:
Updated: 2026-09-22T12:28:59.484Z
Reserved: 2026-09-22T10:38:03.883Z
Link: CVE-2026-95623
Updated: 2026-09-22T12:28:55.315Z
Status : Received
Published: 2026-09-22T11:17:27.357
Modified: 2026-09-22T13:17:13.433
Link: CVE-2026-95623
No data.
OpenCVE Enrichment
Updated: 2026-09-22T12:30:07Z
-
CWE-918
Server-Side Request Forgery (SSRF)