GHSA-v2x6-wwfw-r2rq
MEDIUMAgentgateway is missing parameter sanitization in MCP to OpenAPI conversion
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/agentgateway/agentgatewayReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
When converting MCP tools/call request to OpenAPI request, input path, query, and header values are not sanitized.
Details
When using the MCP to OpenAPI feature, the proxy lacks proper sanitization of input parameters in the MCP call, allowing:
- Injection of additional path or query parameters.
- Injection of additional headers.
Impacted Versions
This vulnerability is fixed in Agentgateway v0.12.0+. Users on older versions are recommended to upgrade to v0.12.0+.
This feature only impacts usage of the MCP to OpenAPI feature
Credits
Agentgateway extends its thanks to @spacewander for the report!
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/agentgateway/agentgateway | all versions | 0.12.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/agentgateway/agentgateway. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/agentgateway/agentgateway to 0.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v2x6-wwfw-r2rq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-v2x6-wwfw-r2rq is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-v2x6-wwfw-r2rq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v2x6-wwfw-r2rq in your dependencies?
O3 detects GHSA-v2x6-wwfw-r2rq across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.