NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

Obot: MCP Registry API readable without authenticationGHSA-pr6h-vr44-xq8j

MEDIUM

GHSA-pr6h-vr44-xq8j is a medium-severity (CVSS 5.3) CWE-862 vulnerability in github.com/obot-platform/obot. A fix is available for github.com/obot-platform/obot — see the affected versions and patch details below.

Also known asCVE-2026-101063GO-2026-6525
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-pr6h-vr44-xq8j.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk
0.00%0.25%0.50%0.74%0.2%0.2%Oct 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/obot-platform/obot

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

In affected versions, enabling registry authentication (OBOT_SERVER_ENABLE_REGISTRY_AUTH=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 OBOT_SERVER_ENABLE_REGISTRY_AUTH=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 contain names, descriptions, repository URLs, icons, and connect URLs — not secret env/header values. This is the same root cause as GHSA-vw82-7fv8-r6gp, whose fix protected /mcp-connect/ but not the /v0.1 registry prefix.

Impact

Worst case is disclosure of the registry server inventory (names, descriptions, repository URLs, connect URLs) that the operator explicitly chose to put behind authentication. No credential values are exposed and unauthenticated users cannot connect to the servers because connecting is properly protected by auth.

Mitigation

Upgrade to v0.23.0 or later, in which the /v0.1 registry prefix is treated as a protected route so authentication is enforced for unauthenticated callers.

Severity

CVSS v3.1 Score: 5.3/10 (Medium) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Credits

The Obot team would like to thank HE WEI（ギカク）(https://www.linkedin.com/in/gikaku, @hewei-gikaku) for responsibly disclosing this issue in accordance with our security policy.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/obot-platform/obotall versions0.23.0go get github.com/obot-platform/obot@v0.23.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/obot-platform/obot, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/obot-platform/obot to 0.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pr6h-vr44-xq8j is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

## Summary In affected versions, enabling registry authentication (`OBOT_SERVER_ENABLE_REGISTRY_AUTH=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 `OBOT_SERVER_ENABLE_REGISTRY_AUTH=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
O3 Security · Impact-Aware SCA

Is GHSA-pr6h-vr44-xq8j in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Obot: MCP Registry API readable without authentication