CVE-2026-130764

Obot OAuth token requests could reach internal services

obot-platform · obot

First documented disclosure · Review checkpoint

Summary

A Power User could redirect token exchange or refresh requests into the server's internal network.

Severity and exploitation evidence

High · 8.3/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

OAuth token endpoints used a client without outbound checks and followed redirects.

Conditions required

A Power User or higher can register a remote MCP server controlled by the attacker.

Potential impact

Internal requests can occur and error-response bodies can be disclosed. Successful response bodies and arbitrary request headers are not available.

Affected versions and configurations

obot: 0.8.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

Apply outbound restrictions to every stage of an OAuth connection.

Evidence and limits

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

Sources