Obot versions before v0.23.0 fail to enforce authentication on MCP Registry endpoints under /v0.1/* when registry authentication is enabled. Unauthenticated attackers can read registry metadata including server names, descriptions, repository URLs, and connect URLs by sending GET requests to /v0.1/servers.
CVE-2026-101063
MEDIUMPre-NVD 5.35.3—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.3 from GitHub Security Advisory published 2026-09-27. A secondary CVSS source baseline 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMhigh confidence
- EG Risk
- 39EG Risk 39/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 computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.2%
- EPSS %ILE
- 14th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 28, 2026
Advisory Details (2)
Auto-updated Sep 27, 2026Patch available. Sources: github.
generic
Obot before v0.23.0 Authentication Bypass via Registry API | Advisories | VulnCheck
https://www.vulncheck.com/advisories/obot-before-0.23.0-authentication-bypass-via-registry-apigithub Patch Available
MCP Registry API readable without authentication · Advisory · obot-platform/obot · GitHub
https://github.com/obot-platform/obot/security/advisories/GHSA-pr6h-vr44-xq8jVendor Advisories for CVE-2026-101063(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| 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 23× in last 7d / 23× 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.
- 2026-10-03 20:28 UTCEG score recompute
- 2026-10-03 20:28 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-02 21:19 UTCEG score recompute
- 2026-10-02 21:19 UTCGHSA enrichment
- 2026-10-01 22:10 UTCEG score recompute
- 2026-10-01 22:09 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-09-30 22:55 UTCEG score recompute
- 2026-09-30 22:55 UTCGHSA enrichment
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-29 23:46 UTCEG score recompute
- 2026-09-29 23:46 UTCGHSA enrichment
- 2026-09-29 15:20 UTCEPSS rescore
- 2026-09-28 21:13 UTCGHSA enrichment
- 2026-09-28 14:26 UTCEG score recompute
- 2026-09-28 14:26 UTCGHSA enrichment
- 2026-09-28 13:57 UTCEG score recompute
- 2026-09-28 13:57 UTCGHSA enrichment
- 2026-09-28 13:50 UTCEPSS rescore
- 2026-09-27 21:25 UTCEG score recompute
- 2026-09-27 21:00 UTCEG score recompute
- 2026-09-27 21:00 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
3 shownGo:github.com/obot-platform/obot
Frequently asked(5)
What is CVE-2026-101063?
CVE-2026-101063 is a medium vulnerability published on September 27, 2026. Obot versions before v0.23.0 fail to enforce authentication on MCP Registry endpoints under /v0.1/* when registry authentication is enabled. Unauthenticated attackers can read registry metadata including server names, descriptions, repository URLs, and connect URLs by sending GET requests to…
When was CVE-2026-101063 disclosed?
CVE-2026-101063 was first published on September 27, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101063 actively exploited?
CVE-2026-101063 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101063?
CVE-2026-101063 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101063?
A fix for CVE-2026-101063 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-101063 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-101063
Is Your Infrastructure Affected by CVE-2026-101063?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.