github.com/obot-platform/obot · Obot: Server-Side Request Forgery via remote MCP server URL
Affects github.com/obot-platform/obotSource GCVE Database
CVSS 7.6 High : upgrade to 0.23.0 soon.
Data as of 19 Sep 2026, 01:56 UTC
- Patch
- Available – fixed in 0.23.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:NWhat to do
Upgrade github.com/obot-platform/obot to 0.23.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/obot-platform/obot | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Obot version 0.23.0 or later, which implements a uniform outbound egress filter rejecting loopback, link-local (including 169.254.169.254), RFC1918 private IP ranges, and IPv6 ULA addresses at dial time. This fix prevents SSRF to internal and cloud metadata endpoints. No additional mitigations are required if upgraded.
Description
Obot versions up to 0.22.1 have a server-side request forgery (SSRF) vulnerability where privileged users can register remote MCP server URLs that Obot fetches without proper destination validation. This allows requests to internal network services and the cloud metadata endpoint (169.254.169.254), potentially exposing cloud IAM credentials. The vulnerability is fixed in version 0.23.0 by enforcing outbound egress restrictions on loopback, link-local, private IP ranges, and IPv6 ULA addresses.