CVE-2026-101062

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-27. A secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 27, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 27, 2026
Patch available. Sources: github.
generic

Obot before v0.23.0 Authentication Bypass via OAuth Dynamic Client Registration | Advisories | VulnCheck

https://www.vulncheck.com/advisories/obot-before-0.23.0-authentication-bypass-via-oauth-dynamic-client-registration
github Patch Available

OAuth Dynamic Client Registration Enables API Token Theft via Audience Confusion · Advisory · obot-platform/obot · GitHub

https://github.com/obot-platform/obot/security/advisories/GHSA-xwmw-prc4-v3cr

Vendor Advisories for CVE-2026-101062(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/obot-platform/obot—0.23.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 31× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 12:40 UTCGHSA enrichment
  2. 2026-10-04 00:32 UTCEG score recompute
  3. 2026-10-04 00:32 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 12:26 UTCGHSA enrichment
  6. 2026-10-03 00:19 UTCEG score recompute
  7. 2026-10-03 00:19 UTCGHSA enrichment
  8. 2026-10-02 12:12 UTCGHSA enrichment
  9. 2026-10-02 00:02 UTCEG score recompute
  10. 2026-10-02 00:02 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 11:39 UTCGHSA enrichment
  13. 2026-09-30 23:31 UTCEG score recompute
  14. 2026-09-30 23:31 UTCGHSA enrichment
  15. 2026-09-30 22:26 UTCEG score recompute
  16. 2026-09-30 22:26 UTCGHSA enrichment
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-30 11:53 UTCGHSA enrichment
  19. 2026-09-29 23:46 UTCEG score recompute
  20. 2026-09-29 23:46 UTCGHSA enrichment
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-29 09:19 UTCEG score recompute
  23. 2026-09-29 09:19 UTCGHSA enrichment
  24. 2026-09-28 21:13 UTCEG score recompute
  25. 2026-09-28 21:13 UTCGHSA enrichment
Show 6 more
  1. 2026-09-28 13:50 UTCEPSS rescore
  2. 2026-09-28 09:32 UTCEG score recompute
  3. 2026-09-28 09:32 UTCGHSA enrichment
  4. 2026-09-27 21:26 UTCEG score recompute
  5. 2026-09-27 21:00 UTCEG score recompute
  6. 2026-09-27 21:00 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-101062?
CVE-2026-101062 is a high vulnerability published on September 27, 2026. Obot before v0.23.0 (affected versions <= v0.22.1) running with OBOTSERVERENABLE_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…
When was CVE-2026-101062 disclosed?
CVE-2026-101062 was first published on September 27, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101062 actively exploited?
CVE-2026-101062 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101062?
CVE-2026-101062 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101062?
A fix for CVE-2026-101062 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-101062 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-101062

Explore →

Is Your Infrastructure Affected by CVE-2026-101062?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs