CVE-2026-88257

BeamMCP advertised nested constraints that it did not enforce

ScriptKittyOS · beam_mcp

First documented disclosure · Review checkpoint

Summary

Tool dispatch could receive arguments prohibited by the advertised schema.

Severity and exploitation evidence

Medium · 5.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

Validation checked only top-level constraints and ignored nested and unsupported schema keywords.

Conditions required

An MCP client can call tools whose host relies on the declared nested constraints.

Potential impact

Unexpected nested keys, values or array items can reach host code; the host's behavior determines the resulting harm.

Affected versions and configurations

beam_mcp: 0.1.0 through versions before 0.10.1.

Fix and mitigation status

0.10.1; unsupported schema keywords now fail startup, so integrations must check their schemas.

Practical next steps

Apply the issue-specific correction: 0.10.1; unsupported schema keywords now fail startup, so integrations must check their schemas. Restrict the affected tool or endpoint until the correction is deployed.

Operating lesson

Enforce every advertised constraint or reject the unsupported schema.

Evidence and limits

Earliest reviewed public evidence 2026-09-26; CVE publication 2026-10-08. CVSS 4.0 5.3 is attributed to EEF in the CNA record.

Sources