High (AgentArmorHQ estimate)Supply chain

Obot: Server-Side Request Forgery via remote MCP server URL

Product
Obot
Affected
Obot <= v0.22.1
Fixed in
0.23.0

Last verified against sources: October 26, 2026

Am I affected?

Obot: affected Obot <= v0.22.1. Fixed in 0.23.0.

  • Check your version: run go list -m github.com/obot-platform/obot. Versions < 0.23.0 of github.com/obot-platform/obot are affected. [1]

What to do now

  1. Upgrade to the fixed version: run go get github.com/obot-platform/obot@v0.23.0 (first patched version 0.23.0). [1]
  2. Upgrade to v0.23.0 or later. [1]

General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.

Discuss this incident

What happened

  • A remote MCP server's URL is set by the user at registration, and Obot fetches that URL from its own server without checking where it points. [1]
  • Obot blocks none of loopback, private network ranges, or the cloud metadata address 169.254.169.254. [1]
  • The fetch also runs automatically when Obot reconciles servers, so registering the server is enough to trigger it. [1]

Impact

  • An attacker with the Power User, Power User Plus, or Admin role can make Obot send requests to internal-only services. [1]
  • The attacker can read the response, because Obot shows the fetched body in its error messages. [1]
  • Against the cloud metadata address 169.254.169.254, this can expose the host's cloud IAM credentials and let the attacker move into the cloud account. [1]

What was done

  • The Obot team released v0.23.0, which adds a single outbound egress checkpoint that rejects loopback, link-local (including 169.254.169.254), RFC1918, and IPv6 ULA addresses when the connection is made. [1]
  • The advisory gives the issue a CVSS v3.1 score of 7.6 out of 10 (High). [1]

Sources

  1. GHSA-jgh3-fggc-mcpm — GitHub Advisory Database

Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.

Share advisory brief with your team

Copy a plain-text summary for Slack, GitHub issues, or team security channels.

Brief
Obot: Server-Side Request Forgery via remote MCP server URL
Product: Obot | Affected: Obot <= v0.22.1 | Fixed in: 0.23.0
Summary: A remote MCP server's URL is set by the user at registration, and Obot fetches that URL from its own server without checking where it points.
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/09/ghsa-jgh3-fggc-mcpm-obot
Was this page useful?

Corrections

Report an error or request a correction. We review requests within 5 business days and add a dated correction note.

10 to 2,000 characters. A link to a source helps. Stored as plain text.

Discussions for Obot

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Check before you install

Paste a package name or a GitHub link and get a clear answer in seconds: Block, Review or No known issues. No account needed.

Check a package

Questions? Contact us