CVE-2026-112077: radareorg radare2 HTTP Sandbox Policy rtr_http.inc.c r_core_cmd_str_pipe protection mechanism
A vulnerability was detected in radareorg radare2 6.2.0/6.2.2. This issue affects the function rcorecmdstrpipe in the library libr/core/rtrhttp.inc.c of the component HTTP Sandbox Policy Handler. Performing a manipulation results in protection mechanism failure. Remote exploitation of the attack is possible. The attack is considered to have high complexity. The exploitability is assessed as difficult. Upgrading to version 6.2.4 is capable of addressing this issue. The patch is named 18fd12efa98a7d1977de7bdd379d8a848777b90f. Upgrading the affected component is recommended. The pre-requisite of the vulnerability is reflected by the CVSS vector. One of the project maintainers explains: "There is a real sandbox configuration issue here, but the report overstates it. The HTTP server defaults to http.sandbox=true, so commands received through /cmd temporarily enable cfg.sandbox. However, cfg.sandbox.grain defaults to all, which means all sandbox capabilities - including exec - remain allowed. Therefore enabling the HTTP sandbox alone does NOT prevent commands from spawning processes. This only matters when the HTTP command endpoint is reachable by someone you do not trust. It is not a remote vulnerability by default: the HTTP server must first be started and exposed to the attacker."
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
radareorg/radare2to a version that resolves this vulnerability.Fixed in 6.2.4Patch 18fd12efa98a7d1977de7bdd379d8a848777b90f
Event History
Frequently Asked Questions
Which deployments are realistically exposed?
Exposure requires the radare2 HTTP command endpoint to be reachable by someone who is not trusted. The issue affects the HTTP Sandbox Policy Handler and is remotely exploitable under that condition.
Does the default HTTP sandbox setting prevent process execution?
No. Although the HTTP server defaults to http.sandbox=true and /cmd temporarily enables cfg.sandbox, cfg.sandbox.grain defaults to all, including the exec capability. Enabling the HTTP sandbox alone therefore does not prevent commands from spawning processes.
What versions should be remediated?
The affected versions identified are radare2 6.2.0 and 6.2.2. Upgrade to version 6.2.4, which addresses the issue with patch 18fd12efa98a7d1977de7bdd379d8a848777b90f.
What can be done if an upgrade cannot happen immediately?
Ensure the HTTP command endpoint is not reachable by untrusted users. The described risk only applies when an untrusted party can access that endpoint.