CVE-2026-101062: obot · Incorrect Authorization
Affects obotSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 0.23.0 soon.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.23.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade obot and obot-platform/obot to 0.23.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| obot-platformobot | Affected
| Fixed in
|
GitHubobot-platform/obotpkg:github/obot-platform/obotOther threats | 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, which adds a consent screen, restricts OAuth tokens to the MCP server involved, and enforces audience validation. These changes prevent unauthorized client registration and token misuse. Until upgrade, avoid enabling OBOT_SERVER_ENABLE_AUTHENTICATION=true in production or restrict access to the dynamic client registration endpoint.
Description
CVE-2026-101062 is a high-severity authorization vulnerability in obot-platform's obot product versions before 0.23.0. When OBOT_SERVER_ENABLE_AUTHENTICATION=true, the OAuth dynamic client registration endpoint is exposed without authentication or restrictions on redirect URIs. This allows an attacker to register a malicious client and trick a logged-in user into authorizing it, resulting in the attacker obtaining an access token with the victim's full group privileges. The token is accepted by obot APIs without proper audience validation, enabling unauthorized access to victim resources. Version 0.23.0 fixes this by adding a consent screen, restricting token scope to the MCP server, and enforcing audience validation.