CVE-2026-101062 Obot before v0.23.0 Authentication Bypass via OAuth Dynamic Client Registration
Attackers can bypass authentication via OAuth dynamic client registration to access victim resources if authentication is enabled but consent is missing.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-101062?
CVE-2026-101062 is a high-severity authentication bypass vulnerability in obot-platform obot, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-863
Which versions are affected by CVE-2026-101062?
3 open source packages ship an affected version, including github.com/obot-platform/obot.
| Package | Affected | Fixed in |
|---|---|---|
github.com/obot-platform/obot Go | All versions | 0.23.0 |
github.com/obot-platform/obot Go | All versions | 0.23.0 |
github.com/obot-platform/obot Go | All versions | 0.23.0 |
How do I fix CVE-2026-101062?
Upgrade github.com/obot-platform/obot to 0.23.0 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-101062 being exploited?
There is no known exploitation of CVE-2026-101062 in the wild and no public exploit code.
Sources
Also known as GHSA-cfp9-746c-5jrw, GHSA-xwmw-prc4-v3cr, GO-2026-6530.