rails-mcp-server 1.4.0 through 1.6.0 OS Command Execution via execute_ruby PTY Escape
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| maquina-app | rails-mcp-server | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Maquina-app | Rails-mcp-server |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.235% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Maquina-app
Maquina-app rails-mcp-server |
|
| Vendors & Products |
Maquina-app
Maquina-app rails-mcp-server |
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | rails-mcp-server 1.4.0 through 1.6.0 OS Command Execution via execute_ruby PTY Escape | |
| Weaknesses | CWE-78 | |
| References |
| |
| Metrics |
cvssV3_1
|