CVE-2026-130766
Deferred Deferred - Pending Action

Obot Remote Access Token Theft via MCP Server Metadata

Vulnerability report for CVE-2026-130766, 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.26.0 before 0.27.0 fails to validate the resource identifier in remote MCP server protected resource metadata, allowing malicious MCP servers to steal access tokens. Attackers can name a different service and authorization server with chosen scopes, causing Obot to obtain the victim's token for that service and forward it to the attacker.

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.26.0 (inc) to 0.27.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Obot versions 0.26.0 to 0.26.3 fail to validate the resource identifier in remote MCP server protected resource metadata. This allows malicious MCP servers to manipulate metadata to steal access tokens. Attackers can name a different service and authorization server with chosen scopes, causing Obot to obtain the victim's token for that service and forward it to the attacker.

Detection Guidance

To detect this vulnerability, check the Obot version running on your system. If it is between 0.26.0 and 0.26.3, it is vulnerable. Run: obot --version. Upgrade to version 0.27.0 or later to mitigate the issue.

Impact Analysis

An attacker could gain unauthorized access to your sensitive data on the targeted service using the stolen token. This could lead to data theft, modification, or other malicious actions depending on the permissions granted. The attack requires a malicious server, victim approval, and a vulnerable Obot version.

Compliance Impact

This vulnerability could lead to unauthorized access to personal or sensitive data, violating GDPR's data protection principles and HIPAA's security requirements. Organizations using Obot may face compliance violations, legal penalties, and reputational damage due to potential data breaches.

Mitigation Strategies

Upgrade Obot to version 0.27.0 or later to enforce strict validation of resource metadata and prevent token theft.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130766. 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...