GHSA-pr6h-vr44-xq8j: Obot MCP Registry API Readable Without Vulnerability

MODERATE
CVSS 5.3
CWE-862 CWE-863
Published
Advisory Summary

GHSA-pr6h-vr44-xq8j is a MODERATE (CVSS 5.3) mcp registry api readable without vulnerability (CWE-862: Missing Authorization) affecting Obot libraries in the Go ecosystem. The issue involves mcp registry api readable without authentication. Remediation is available by upgrading affected packages to version 0.23.0.

GHSA-pr6h-vr44-xq8j at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-pr6h-vr44-xq8j
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-862: Missing Authorization
Affected Product Obot
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix GHSA-pr6h-vr44-xq8j

To remediate this vulnerability, upgrade all affected Obot dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/obot-platform/obot fixed: 0.23.0
Upgrade github.com/obot-platform/obot to 0.23.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/obot-platform/obot

How to Check if You Are Affected

To determine whether your application is affected by GHSA-pr6h-vr44-xq8j, inspect your project dependencies for Obot:

inspect dependencies for github.com/obot-platform/obot

Analyze the terminal output to locate any version of Obot in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.23.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-862: Missing Authorization, where the product does not perform an authorization check when an actor attempts to access a resource or perform an action. In Obot, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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](https://github.com/hewei-gikaku)) for responsibly disclosing this issue in accordance with our [security policy](https://github.com/obot-platform/obot/?tab=security-ov-file).

GHSA-pr6h-vr44-xq8j Affected Obot Versions

1 component(s)
Fixed Versions:
0.23.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/obot-platform/obot
Go
< 0.23.0
0.23.0

References

Frequently Asked Questions

What is GHSA-pr6h-vr44-xq8j?
GHSA-pr6h-vr44-xq8j is a security vulnerability in Obot involving MCP Registry API readable without authentication under CWE-862: Missing Authorization.
Which Obot versions are affected?
Affected versions include releases prior to 0.23.0 across affected packages: github.com/obot-platform/obot.
What version fixes GHSA-pr6h-vr44-xq8j?
Upgrading to 0.23.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/obot-platform/obot affected?
Yes, github.com/obot-platform/obot is affected in releases prior to 0.23.0. Upgrade your dependency to 0.23.0 or later.
What is the CVSS score of GHSA-pr6h-vr44-xq8j?
GHSA-pr6h-vr44-xq8j has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with GHSA-pr6h-vr44-xq8j?
GHSA-pr6h-vr44-xq8j is classified under CWE-862: Missing Authorization (The product does not perform an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Go dependencies for GHSA-pr6h-vr44-xq8j?
Run the dependency tree command: 'inspect dependencies for github.com/obot-platform/obot'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pr6h-vr44-xq8j",
  "modified" : "2026-09-18T17:59:41Z",
  "published" : "2026-09-18T17:59:40Z",
  "aliases" : [ ],
  "summary" : "Obot: MCP Registry API readable without authentication",
  "details" : "## Summary\n\nIn 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.\n\n## Am I affected?\n\nYou 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.)\n\n## Details\n\nThe 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.\n\n## Impact\n\nWorst 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.\n\n## Mitigation\n\nUpgrade 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.\n\n## Severity\n\nCVSS 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`\n\n## Credits\n\nThe Obot team would like to thank HE WEI(ギカク)(https://www.linkedin.com/in/gikaku, [@hewei-gikaku](https://github.com/hewei-gikaku)) for responsibly disclosing this issue in accordance with our [security policy](https://github.com/obot-platform/obot/?tab=security-ov-file).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/obot-platform/obot"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.23.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/obot-platform/obot/security/advisories/GHSA-pr6h-vr44-xq8j"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/obot-platform/obot"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/obot-platform/obot/releases/tag/v0.23.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-862", "CWE-863" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-18T17:59:40Z",
    "nvd_published_at" : null
  }
}