Skip to content
Threat Brief

← All advisories

CVE-2026-104634

Low 2.3No known exploitationFix available

beam_mcp: JSON boolean and null tool arguments reach dispatch as strings

Record last updated

CVSS score

2.3

Low on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

None

No EPSS score available

CISA remediation deadline

None

Not in the KEV catalog

Description

Incorrect Type Conversion or Cast vulnerability in BeamMCP.Server in ScriptKittyOS beam_mcp allows an MCP client's JSON true, false and null tool arguments to reach the host's dispatch function as the strings "true", "false" and "nil". After BeamMCP.Schema.validate/2 accepted a value as a boolean, normalize_arguments/2 passed every argument through to_json_value/1, whose atom clause converts true, false and nil to strings. A string is truthy in Elixir, so a host that tests a boolean argument, for example if args.dry_run, takes the opposite branch for false, and a guard such as confirm: false reads as set. The client controls the argument and could send true directly, so the practical impact is limited to hosts whose behaviour on false differs from their behaviour on true, and to any policy layer in front of the server that permits false but refuses true. The same normalisation applies to prompts/get arguments, which exist from 0.5.0. This issue affects beam_mcp: from 0.1.0 before 0.10.1.

Weakness: CWE-704

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
In the host's dispatch function, compare boolean arguments against both forms, for example args.flag in [true, "true"] and args.flag in [false, "false"], and treat the string "nil" as null where the schema admits null. Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
ScriptKittyOSbeam_mcpfrom 0.1.0 before 0.10.10.10.1CVE Program
ScriptKittyOSbeam_mcpfrom 083838eb8e17fe5f6fcaf761bdbe203110288b0b before 289dbdbad641943b29a3b8d1eb36506cc8cec10a289dbdbad641943b29a3b8d1eb36506cc8cec10aCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references