Obot: MCP Registry API readable without authentication

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2026-101063: 0.24% estimated exploitation activity in the next 30 days; percentile 15.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary In affected versions, enabling registry authentication (OBOTSERVERENABLEREGISTRYAUTH=true) does not actually protect the MCP Registry endpoints under /v0.1/ — they remain readable by unauthenticated callers. Am I affected? You are affected if you run Obot <= v0.22.1 with OBOTSERVERENABLEREGISTRYAUTH=true. An unauthenticated GET /v0.1/servers returns 200 OK with catalog server metadata. (With registry auth disabled, the registry is intentionally public and this is not a defect.) Details The authorizer rejects a fixed set of known-protected prefixes and then default-allows everything else. The registry is mounted at the top-level /v0.1 prefix, which was not in that set, so anonymous requests were authorized before the WWW-Authenticate challenge for /v0.1 was ever reached. The registry handler still applies its own per-user ACR filtering, so an anonymous caller receives only entries accessible to the anonymous identity (e.g. default-catalog/wildcard entries), and responses…

Published by the source

18 Sep 2026, 17:59 UTC

Last modified by the source

28 Sep 2026, 17:10 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pr6h-vr44-xq8j

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6525

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pr6h-vr44-xq8j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-101063

Advisory: Obot: MCP Registry API readable without authentication
IDs: CVE-2026-101063, GHSA-pr6h-vr44-xq8j
Record: https://patchnext.com/advisories/cve-2026-101063 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/obot-platform/obot 0.23.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/obot-platform/obot: affected < 0.23.0; fixed in 0.23.0

## Suggested inspection (read-only)
- Go github.com/obot-platform/obot: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/obot-platform/obot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pr6h-vr44-xq8j (OSV record GHSA-pr6h-vr44-xq8j lists affected ranges: Go github.com/obot-platform/obot >=0 <0.23.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6525 (OSV record GO-2026-6525 lists affected ranges: Go github.com/obot-platform/obot >=0 <0.23.0 (fixed))
- Verified: https://github.com/advisories/GHSA-pr6h-vr44-xq8j (GitHub-reviewed advisory GHSA-pr6h-vr44-xq8j lists affected ranges: Go github.com/obot-platform/obot >=0 <0.23.0)

Commands are suggestions: review each one before running it.