github.com/obot-platform/obot · Obot: OAuth Dynamic Client Registration Enables API Token Theft via Audience Confusion
Affects github.com/obot-platform/obotSource GCVE Database
CVSS 8.8 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:N/UI:R/S:U/C:H/I:H/A:HWhat 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. The update introduces a consent screen that displays the requesting client and MCP server before authorization completes, restricts tokens to the MCP server involved in the request, and enforces audience validation to ensure tokens are only accepted for their intended MCP server. These protections prevent unauthorized token issuance and misuse. No other mitigation is required if updated.
Description
Obot versions up to 0.22.1 with authentication enabled are vulnerable to an OAuth dynamic client registration flaw that allows an attacker to steal API tokens via audience confusion. An unauthenticated attacker can register an OAuth client with an arbitrary redirect URI, and the authorization flow auto-completes without user consent. If a logged-in user visits a crafted authorization URL, the attacker receives an authorization code that can be exchanged for an access token carrying the victim's full group permissions. This token can be used against API endpoints the victim is authorized for, enabling unauthorized access until token revocation. The vulnerability is fixed in version 0.23.0 with added consent screens, token audience restrictions, and validation.