Server-Side Request Forgery via Unrestricted HTTP Redirection in MCP Toolbox
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mcp-toolbox | unaffected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mcp-toolbox |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.133% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/googleapis/mcp-toolbox/pull/3448 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google mcp-toolbox |
|
| Vendors & Products |
Google
Google mcp-toolbox |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A Server-Side Request Forgery (SSRF) vulnerability exists in the generic HTTP source and tool components of Google mcp-toolbox versions 0.3.0 through 1.4.0. While the toolbox implements baseline input sanitization for user-controlled parameters, the underlying HTTP client (internal/sources/http/http.go) fails to safely regulate request redirection boundaries. Specifically, the client is initialized without a restrictive CheckRedirect policy hook and lacks target IP validation. An attacker or a malicious data-driven prompt can supply a crafted path parameter that triggers an open redirect or a direct destination swap on the target backend, coercing the mcp-toolbox into blindly following the redirection and making unauthorized requests to internal or arbitrary external endpoints. | |
| Title | Server-Side Request Forgery via Unrestricted HTTP Redirection in MCP Toolbox | |
| Weaknesses | CWE-918 | |
| References |
| |
| Metrics |
cvssV4_0
|