{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81097 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81097 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81097 is a high-severity command injection vulnerability in maquina-app rails-mcp-server, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81097 and fix it if it is affected.\n\nWhat it is: CVE-2026-81097 is a high-severity command injection vulnerability in maquina-app rails-mcp-server, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81097 in the wild and no public exploit code.\n\nAffected product: maquina-app rails-mcp-server. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-81097/ (Markdown: https://insights.sbomify.com/CVE-2026-81097/index.md)","id":"CVE-2026-81097","markdown":"https://insights.sbomify.com/CVE-2026-81097/index.md","name":"CVE-2026-81097","record":{"aliases":["GHSA-247c-497m-jx82"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruby MCP server library","requires_auth":"none","summary":"Attackers can execute arbitrary OS commands via the execute_ruby tool in rails-mcp-server due to missing pseudo-terminal restrictions in the sandbox.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"The execute_ruby tool is documented as a read-only Ruby sandbox and is enforced by a pattern denylist together with replacements for the process-spawning methods on Kernel. The pseudo-terminal library's spawn entry points are neither in the denylist nor replaced, so a normal tool call could reach them and start a shell, executing commands as the account running the server and outside the guarded methods. The denylist was introduced with the tool in 1.4.0 and never covered those entry points through 1.6.0. Version 1.6.1 restricts the requires the sandbox permits to a data-only list and blocks dynamic dispatch to execution entry points; 2.0.0 removes the tool.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"rails-mcp-server 1.4.0 through 1.6.0 OS Command Execution via execute_ruby PTY Escape","id":"CVE-2026-81097","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Telnyx MCP Server through 6.83.0 Missing Authentication on Streamable HTTP Transport","id":"CVE-2026-81098"},"packages":[],"prev":{"headline":"ToolUniverse through 1.2.6 Unauthenticated Remote Code Execution via python_code_executor Sandbox Escape","id":"CVE-2026-81096"},"products":["rails-mcp-server"],"published":"2026-08-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-08-29","vendors":["maquina-app"]},"summary":"Attackers can execute arbitrary OS commands via the execute_ruby tool in rails-mcp-server due to missing pseudo-terminal restrictions in the sandbox.","url":"https://insights.sbomify.com/CVE-2026-81097/"}