CVE-2026-130768

Obot MCP addresses and icon fetches could bypass outbound restrictions

obot-platform · obot

First documented disclosure · Review checkpoint

Summary

A Power User could probe services that the outbound policy was intended to block.

Severity and exploitation evidence

Medium · 5.1/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

Unspecified and IPv6 transition addresses bypassed checks, while registry icon requests lacked them.

Conditions required

Power User or higher can add remote MCP servers or icons; the internal destinations are otherwise prohibited by policy.

Potential impact

Blind internal requests reveal reachability. Ordinary target response bodies are not exposed; a destination speaking MCP can have different behavior.

Affected versions and configurations

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

Normalize alternate address forms and apply outbound checks to auxiliary fetches.

Evidence and limits

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

Sources