cve.bz

CVE-2026-101084 obot-platform obot

9.3 criticalEPSS 0.3%Fix available

Critical (9.3) in obot-platform obot. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/obot-platform/obot 0.21.1.

On this page
obot versions before v0.21.1 fail to enforce Access Control Rules on the /mcp-connect endpoint, allowing any authenticated user to connect to restricted MCP servers if they possess the server ID. Attackers can bypass authorization checks to access and manipulate sensitive backend systems through MCP tool calls using stored OAuth credentials.

Severity

CVSS 4.0

9.3 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

CVSS 3.1

9.6 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

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

Ask an AI about this CVE

Show the promptExplain CVE-2026-101084 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-101084?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-101084?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-101084 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
obot-platform obotbefore 0.21.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vw82-7fv8-r6gpGogithub.com/obot-platform/obot<0.21.10.21.1
GO-2026-5678Gogithub.com/obot-platform/obot<0.21.10.21.1

References

Check your stackJSON