CVE-2026-130764
Deferred Deferred - Pending Action

Obot Server-Side Request Forgery via Malicious OAuth Token Endpoint

Vulnerability report for CVE-2026-130764, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-18

Last updated on: 2026-11-18

Assigner: VulnCheck

Description

Obot from 0.8.0 before 0.27.0 contains a server-side request forgery vulnerability that allows Power User accounts to reach internal hosts by advertising a malicious OAuth token endpoint in remote MCP server metadata. Attackers can direct token exchange or refresh requests, including redirected GET requests, to cloud metadata services or private-network hosts and read error response bodies.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-18
Last Modified
2026-11-18
Generated
2026-11-19
AI Q&A
2026-11-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
obot_platform obot From 0.8.0 (inc) to 0.27.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in the Obot platform affecting versions 0.8.0 to 0.26.3. It occurs when Obot exchanges or refreshes OAuth tokens for a remote MCP server without validating the token endpoint. Attackers with sufficient privileges can register a malicious remote MCP server and direct token requests to internal hosts or cloud metadata services. If these services respond with errors, their response bodies are exposed to the attacker.

Detection Guidance

To detect this SSRF vulnerability in Obot, monitor network traffic for OAuth token exchange requests originating from Obot servers to internal or unexpected external hosts. Check Obot logs for OAuth callback errors that expose internal service responses. Review MCP server configurations for unauthorized remote endpoints pointing to internal addresses.

Impact Analysis

An attacker could access internal network resources or cloud metadata services by exploiting this flaw. They may read sensitive error responses from internal hosts, potentially exposing confidential data. The impact includes unauthorized access to internal systems and data leaks, though it requires an account with privileges to add remote MCP servers.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating confidentiality requirements in GDPR and HIPAA. Exposure of internal error responses may result in data breaches, triggering compliance violations and potential regulatory penalties.

Mitigation Strategies

Immediately upgrade Obot to version 0.27.0 or later to enforce egress checks and block internal destinations. Disable or restrict the ability to register remote MCP servers for non-admin users. Monitor network traffic for suspicious OAuth token requests to internal hosts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130764. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...