CVE-2026-101062
Last modified
CVE-2026-101062 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| obot-platform | obot | < 0.23.0 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-101062?
How severe is CVE-2026-101062?
How do I fix CVE-2026-101062?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-101057utcp-mcp (the MCP plugin of python-utcp) through 1.1.2 conne…3.1
- CVE-2026-101058python-utcp (pip package utcp-http) before 1.1.12 does not v…6.9
- CVE-2026-101059utcp-http before 1.1.4 fails to validate the OAuth2 tokenUrl…7.1
- CVE-2026-10106Mattermost versions 11.7.x <= 11.7.2, 11.6.x <= 11.6.4, 10.1…6.5
- CVE-2026-101060python-utcp versions before 1.1.4 contain a server-side requ…8.2
- CVE-2026-101061utcp-gql before 1.1.1 and utcp-websocket before 1.1.1 contai…4.7
- CVE-2026-101063Obot versions before v0.23.0 fail to enforce authentication …5.3
- CVE-2026-101064Obot before v0.23.0 contains a server-side request forgery v…7.6
- CVE-2026-101065Obot is an open-source AI agent/MCP platform. In all version…9.8
- CVE-2026-101066A vulnerability was determined in dbgate up to 7.3.1. The im…7.3
- CVE-2026-101067A vulnerability was identified in dbgate up to 6.8.1/7.0.2/7…7.3
- CVE-2026-101068A security flaw has been discovered in dbgate up to 7.3.1. T…6.5
Are you affected by CVE-2026-101062?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
