Path Traversal Vulnerability in googleapis/mcp-toolbox HTTP Tool
- Severity
- HIGH
- Affected component
- mcp-toolbox (go)
- Affected versions
- < 1.3.0
- Patched version
- Not yet available
An early warning has been issued for a path traversal vulnerability in the HTTP tool URL builder of googleapis/mcp-toolbox. This vulnerability allows an attacker to escape the operator-configured path scope and make requests to unintended endpoints on the same target host.
What happened
A path traversal vulnerability has been reported in the HTTP tool URL builder of googleapis/mcp-toolbox. This vulnerability, tracked as GHSA-VWXW-JRG6-9JXV, allows an attacker to escape the operator-configured path scope and make requests to unintended endpoints on the same target host. The vulnerability affects versions of mcp-toolbox prior to 1.3.0. The issue has been identified and is under investigation. It is recommended to upgrade to version 1.3.0 or higher once it becomes available.
The vulnerability was first flagged on June 29, 2026. It has not been exploited in the wild as of the latest reports. The primary source for this vulnerability is the GitHub Advisory Database, which provides detailed information on the affected components and recommended actions.
What to do about it
- Upgrade to version 1.3.0 or higher of mcp-toolbox once it becomes available.
- Review the usage of path parameters in your applications to prevent potential exploitation.
- Monitor the primary sources for updates on the vulnerability and any available patches.
- Implement additional security measures to restrict access to sensitive endpoints.
- Conduct a security audit of your application to identify and mitigate similar vulnerabilities.
How 0Day would have caught this
mcp-toolbox is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.
Frequently asked questions
Am I affected?
If you are using mcp-toolbox version 1.2.9 or earlier, you are affected by this vulnerability.
What should I do right now?
Upgrade to version 1.3.0 or higher of mcp-toolbox once it becomes available and review the usage of path parameters in your applications.
Is there an official fix available?
No official fix has been published yet. Monitor the primary sources for updates on the vulnerability and any available patches.
How can I prevent similar vulnerabilities in the future?
Implement strict input validation and sanitization for path parameters, conduct regular security audits, and stay updated with the latest security patches and advisories.