CVE-2026-130766

Obot could send another service's access token to a malicious MCP server

obot-platform · obot

First documented disclosure · Review checkpoint

Summary

Unvalidated resource metadata could bind a legitimate authorization to an attacker-controlled server.

Severity and exploitation evidence

High · 8.8/10 · CVSS 4.0. Severity source.

Exploitation not established: Malicious exploitation remains unverified in the reviewed originals. A demonstration or absence from KEV does not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Obot accepted a resource identifier that did not match the MCP endpoint.

Conditions required

A malicious MCP server, an authorization server supporting accepted client registration and resource indicators, and existing or new victim consent.

Potential impact

The malicious server can receive a token for another service and use the scopes the victim authorized.

Affected versions and configurations

obot: 0.26.0 through versions before 0.27.0.

Fix and mitigation status

0.27.0.

Practical next steps

Apply the issue-specific correction: 0.27.0. Restrict the affected tool or endpoint until the correction is deployed.

Operating lesson

Bind OAuth resource metadata and tokens to the actual tool server.

Evidence and limits

Earliest reviewed public evidence 2026-10-31; CVE publication 2026-11-18. CVSS 4.0 8.8 is attributed to VulnCheck in the CNA record.

Sources