CVE-2026-14540: Server-Side Request Forgery via Unrestricted HTTP Redirection in MCP Toolbox
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-14540?
CVE-2026-14540 has a risk score of 64, indicating a medium severity level.
How do I fix CVE-2026-14540?
To fix CVE-2026-14540, update the Google mcp-toolbox to version 1.4.1 or later.
What impact does CVE-2026-14540 have on my system?
CVE-2026-14540 allows for Server-Side Request Forgery, which could lead to unauthorized access to internal resources.
Which versions are affected by CVE-2026-14540?
CVE-2026-14540 affects Google mcp-toolbox versions 0.3.0 through 1.4.0.
Can CVE-2026-14540 be exploited remotely?
Yes, CVE-2026-14540 can be exploited remotely due to the nature of Server-Side Request Forgery.