Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-104634 Overview
CVE-2026-104634 is an Incorrect Type Conversion or Cast vulnerability [CWE-704] in BeamMCP.Server, part of ScriptKittyOS beam_mcp. The flaw causes JSON true, false, and null values sent as Model Context Protocol (MCP) tool arguments to arrive at the host dispatch function as the strings "true", "false", and "nil". Because every non-nil, non-false value is truthy in Elixir, host code that branches on a boolean argument takes the opposite path when the client sends false. The issue affects beam_mcp from 0.1.0 before 0.10.1, and the same normalisation applies to prompts/get arguments present since 0.5.0.
Critical Impact
An MCP client can flip the server-side meaning of boolean guards such as confirm: false or dry_run: false, bypassing policy or safety checks that depend on the false branch.
Affected Products
- ScriptKittyOS beam_mcp from 0.1.0 before 0.10.1
- BeamMCP.Server tool argument handling
- prompts/get argument handling (introduced in 0.5.0)
Discovery Timeline
- 2026-10-08 - CVE-2026-104634 published to NVD
- 2026-10-08 - Last updated in NVD database
Technical Details for CVE-2026-104634
Vulnerability Analysis
The defect lives in the argument normalisation path between the MCP transport and the host dispatch function. After BeamMCP.Schema.validate/2 accepts a value as a boolean, normalize_arguments/2 routes each argument through to_json_value/1. The atom clause of to_json_value/1 converts the Elixir atoms true, false, and nil into their string representations before forwarding them to the host.
In Elixir, only false and nil are falsy; every other term, including the strings "false" and "nil", is truthy. A host that writes if args.dry_run do ... end therefore executes the true branch even when the client sent JSON false. A guard such as confirm: false is read as set, defeating confirmation checks.
The client controls arguments directly and can already send JSON true, so direct escalation requires a host whose false branch does something the true branch cannot. The more practical risk is a policy layer that inspects and permits false while rejecting true; the host still observes a truthy value and acts as if the client had sent true.
Root Cause
The root cause is an improper type conversion in normalize_arguments/2 and to_json_value/1. The functions coerce validated boolean and null atoms into strings instead of preserving them as JSON-native boolean and null values at the dispatch boundary.
Attack Vector
Exploitation requires an authenticated MCP client sending crafted tool-call or prompts/get requests over the network transport. The attacker submits valid JSON with a boolean set to false or a value set to null, and relies on the server rewriting those values into truthy strings before host code evaluates them.
# Illustrative patch context from the 0.10.1 fix
# Source: https://github.com/ScriptKittyOS/beam_mcp/commit/289dbdbad641943b29a3b8d1eb36506cc8cec10a
@spec decode(kind(), term()) :: {:ok, key()} | {:error, :malformed | {:kind, String.t()}}
def decode(kind, cursor) when is_atom(kind) and is_binary(cursor) do
with {:ok, json} <- Base.url_decode64(cursor, padding: false),
# The wire's one JSON reader (the nesting bound, then the repeated-key refusal), not a
# bare Jason.decode/1: the cursor is client bytes like any other. Before 0.10.1 a
# cursor carried a nest the body itself would have been refused for.
{:ok, %{"v" => @version, "k" => k, "a" => key}} when is_binary(k) and is_binary(key) <-
BeamMCP.JSON.decode(json) do
if k == Atom.to_string(kind), do: {:ok, key}, else: {:error, {:kind, k}}
else
_ -> {:error, :malformed}
end
end
Source: GitHub Commit 289dbd. This patch tightens the shared JSON decoding path; the companion 0.10.1 changes correct the boolean and null normalisation behaviour described above.
Detection Methods for CVE-2026-104634
Indicators of Compromise
- Host logs showing boolean-sensitive tool arguments taking the truthy branch despite client-supplied JSON false.
- Successful execution of operations guarded by dry_run, confirm, or similar flags where the request body contains those keys set to false.
- Dispatch traces containing the literal strings "true", "false", or "nil" where boolean or nil values are expected.
Detection Strategies
- Audit tool handlers for pattern-matching or truthiness checks on arguments and compare the executed branch against the raw JSON payload captured at the transport layer.
- Add server-side assertions that reject non-boolean values for schema-declared boolean fields before dispatch.
- Review policy or proxy layers in front of BeamMCP that treat true and false differently to confirm the host observes the same values the policy evaluated.
Monitoring Recommendations
- Log the fully normalised argument map handed to each tool and alert on type mismatches against the declared schema.
- Track beam_mcp package versions in production inventories and flag any deployment at a version earlier than 0.10.1.
- Correlate MCP request bodies with host-side dispatch outcomes to detect semantic drift between client intent and server behaviour.
How to Mitigate CVE-2026-104634
Immediate Actions Required
- Upgrade beam_mcp to version 0.10.1 or later in all MCP server deployments.
- Enumerate hosts that register tools with boolean or nullable arguments and verify their branches are not being inverted by stringified values.
- Review prompts/get consumers for the same normalisation issue, since the affected path has existed since 0.5.0.
Patch Information
The fix is delivered in beam_mcp0.10.1. The relevant upstream changes are documented in the GitHub Security Advisory GHSA-wv7p-j6qh-3hj4, the ScriptKittyOS commit 289dbd, and the ScriptKittyOS commit 083838e. Additional details are available in the Erlang Ecosystem Foundation CNA advisory and the OSV record EEF-CVE-2026-104634.
Workarounds
- In tool handlers, replace truthiness checks on boolean arguments with explicit comparisons such as args.dry_run == true or pattern matches on true/false atoms.
- Add a pre-dispatch guard that converts string "true", "false", and "nil" back to their atom equivalents when the schema declares boolean or nullable types.
- Where feasible, require clients to omit optional boolean flags rather than send false, until the server is upgraded.
# Pin beam_mcp to the fixed release in mix.exs
# {:beam_mcp, "~> 0.10.1"}
mix deps.update beam_mcp
mix deps.get
mix compile --warnings-as-errors
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

