CVE-2026-104634
BeamMCP converted false tool arguments into truthy strings
ScriptKittyOS · beam_mcp
First documented disclosure · Review checkpoint
Summary
A boolean accepted by schema validation could have different meaning when dispatched.
Severity and exploitation evidence
Low · 2.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.
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
Argument normalization converted false, true and null to strings.
Conditions required
An MCP client can call a host whose policy or dispatch behavior distinguishes boolean values; the client already controls the submitted argument.
Potential impact
Confirmation or other boolean guards can take an unintended branch. Impact depends on host logic and any policy that admits false but denies true.
Affected versions and configurations
beam_mcp: 0.1.0 through versions before 0.10.1.
Fix and mitigation status
0.10.1.
Practical next steps
Apply the issue-specific correction: 0.10.1. Restrict the affected tool or endpoint until the correction is deployed.
Operating lesson
Preserve validated types across tool dispatch boundaries.
Evidence and limits
Earliest reviewed public evidence 2026-09-26; CVE publication 2026-10-08. CVSS 4.0 2.3 is attributed to EEF in the CNA record.
Sources
- EEF CVE authority record
Primary source ·
- Maintainer security advisory
Primary source ·
- Original correction or vendor bulletin
Primary source ·