How severe is GHSA-pr6h-vr44-xq8j?

GHSA-pr6h-vr44-xq8j has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-pr6h-vr44-xq8j?

GHSA-pr6h-vr44-xq8j affects the following packages: github.com/obot-platform/obot (Go). Ecosystems affected: Go.

How do I fix GHSA-pr6h-vr44-xq8j?

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.

How do I detect GHSA-pr6h-vr44-xq8j in my Go dependencies?

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.

How do I mitigate GHSA-pr6h-vr44-xq8j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pr6h-vr44-xq8j?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pr6h-vr44-xq8j can be triaged on real exposure rather than presence alone.

Is GHSA-pr6h-vr44-xq8j actively exploited in the wild?

No public exploit code has been indexed for GHSA-pr6h-vr44-xq8j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-pr6h-vr44-xq8j published, and has it been updated?

GHSA-pr6h-vr44-xq8j was published on September 18, 2026 and was last updated on September 18, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

GHSA-pr6h-vr44-xq8j — obot

MEDIUM

GHSA-pr6h-vr44-xq8j is a medium-severity (CVSS 5.3) 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.

Obot: MCP Registry API readable without authentication

Published

Sep 18, 2026

Updated

Sep 18, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, FIRST.org (EPSS)

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

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/obot-platform/obot`	all versions	0.23.0`go get github.com/obot-platform/obot@v0.23.0`

Detection & mitigation playbook

Open-source dependency

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.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-pr6h-vr44-xq8j can be triaged on real exposure rather than presence alone.

Tailored to GHSA-pr6h-vr44-xq8j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-pr6h-vr44-xq8j across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works