{"answers":{"affected":"1 open source package ship an affected version, including beam_mcp.","exploited":"There is no known exploitation of CVE-2026-104634 in the wild and no public exploit code.","fix":"Upgrade beam_mcp to 0.10.1 or later.","what":"CVE-2026-104634 is a low-severity vulnerability in ScriptKittyOS beam_mcp, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-104634 and fix it if it is affected.\n\nWhat it is: CVE-2026-104634 is a low-severity vulnerability in ScriptKittyOS beam_mcp, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-104634 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- beam_mcp (Hex): affected from 0.1.0; fixed in 0.10.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-104634/ (Markdown: https://insights.sbomify.com/CVE-2026-104634/index.md)","id":"CVE-2026-104634","markdown":"https://insights.sbomify.com/CVE-2026-104634/index.md","name":"CVE-2026-104634","record":{"aliases":["EEF-CVE-2026-104634","GHSA-rcm8-2hxq-3q25","GHSA-wv7p-j6qh-3hj4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir MCP library","requires_auth":"low_privilege","summary":"Incorrect type conversion allows boolean arguments to be treated as strings, potentially bypassing security checks in MCP server implementations.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-704","name":"Incorrect Type Conversion or Cast"}],"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.\n\nThe 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.\n\nThis issue affects beam_mcp: from 0.1.0 before 0.10.1.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"beam_mcp: JSON boolean and null tool arguments reach dispatch as strings","id":"CVE-2026-104634","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"other","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"Uncontrolled recursion in elixir-protobuf/protobuf JSON decoding of self-referential messages","id":"CVE-2026-104635"},"packages":[{"ecosystem":"Hex","fixed":["0.10.1"],"introduced":["0.1.0"],"last_affected":[],"package":"beam_mcp","purl":"pkg:hex/beam_mcp","source":"EEF-CVE-2026-104634"}],"prev":{"headline":"Gitea migration memory exhaustion from zero page size","id":"CVE-2026-104633"},"products":["beam_mcp"],"published":"2026-10-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["ScriptKittyOS"]},"summary":"Incorrect type conversion allows boolean arguments to be treated as strings, potentially bypassing security checks in MCP server implementations.","url":"https://insights.sbomify.com/CVE-2026-104634/"}