# 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.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** Yes
- **Published:** 27 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-cfp9-746c-5jrw, GHSA-xwmw-prc4-v3cr, GO-2026-6530

## 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 (Incorrect Authorization)

## Which versions are affected by CVE-2026-101062?

3 open source packages ship an affected version, including github.com/obot-platform/obot.


| Package | Ecosystem | 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.

## Is CVE-2026-101062 being exploited?

There is no known exploitation of CVE-2026-101062 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101062 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-101062 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/obot-platform/obot (Go): affected all versions; fixed in 0.23.0
- github.com/obot-platform/obot (Go): affected all versions; fixed in 0.23.0
- github.com/obot-platform/obot (Go): affected all versions; fixed in 0.23.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101062/ (Markdown: https://insights.sbomify.com/CVE-2026-101062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101062
- OSV: https://osv.dev/vulnerability/CVE-2026-101062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101062/
Summaries are generated and may contain mistakes; the official description above is the record.