obot before v0.21.1 Authorization Bypass via /mcp-connect
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| obot-platform | obot | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Obot-platform | Obot |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.346% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Obot-platform
Obot-platform obot |
|
| Vendors & Products |
Obot-platform
Obot-platform obot |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | obot before v0.21.1 Authorization Bypass via /mcp-connect | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|