CVE-2026-101062 Details
Description
Obot before v0.23.0 (affected versions <= v0.22.1) running with OBOT_SERVER_ENABLE_AUTHENTICATION=true exposes OAuth dynamic client registration without authentication and without any restriction on the redirect URIs a client may register. Because the authorization flow auto-completes for an already logged-in user with no consent screen, an attacker who registers a client pointing at their own domain and induces a logged-in victim to visit a single crafted authorization URL receives an authorization code at the attacker-controlled redirect URI and can exchange it for an access token and refresh token. The token minted by the MCP OAuth flow carries the victim's full group set in the JWT, and Obot validated only the issuer and not the audience, so the token is accepted as a bearer token against any Obot API endpoint the victim can access rather than being scoped to the requested MCP server, allowing the attacker to read or modify the victim's resources until the token is revoked. v0.23.0 adds a consent screen, restricts MCP OAuth tokens to the MCP involved in the request, and enforces audience validation.
A vulnerability exists in Obot versions prior to 0.23.0, specifically in versions 0.22.1 and earlier, when the authentication feature is enabled. The issue arises from the OAuth dynamic client registration process, which is exposed without authentication and allows arbitrary redirect URIs to be registered. This flaw enables an attacker to register a client with a redirect URI pointing to their own domain. When a logged-in user is induced to visit a crafted authorization URL, the authorization code is sent to the attacker's URI. The attacker can then exchange this code for access and refresh tokens. The access token, which includes the victim's group information, can be used to access any Obot API endpoint the victim has rights to, potentially allowing unauthorized access to the victim's resources until the token is revoked.
Users are advised to upgrade to Obot version 0.23.0 or later, which addresses this vulnerability by introducing a consent screen, restricting OAuth tokens to the relevant MCP server, and enforcing audience validation.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 27, 2026CISA-ADP
Assessed Sep 30, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/obot-platform/obot/security/advisories/GHSA-xwmw-prc4-v3cr | [email protected] | AdvisoryRemedyVendor |
| https://www.vulncheck.com/advisories/obot-before-0.23.0-authentication-bypass-via-oauth-dynamic-client-registration | [email protected] | AdvisoryBundleRemedy |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-863 | Incorrect Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Obot | <= 0.22.1 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 30, 2026 | CVE Modified | CISA-ADP |
| Sep 27, 2026 | New CVE Received | [email protected] |
Volerion