CVE Catalog

CVE-2026-112077

MediumCVSS 5.6
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.29%

20th percentile - higher than 20% of all known CVEs

Summary

A vulnerability was detected in radareorg radare2 in the r_core_cmd_str_pipe function of libr/core/rtr_http.inc.c, related to the HTTP sandbox policy handler. Manipulation results in a protection mechanism failure, and remote exploitation is possible though highly complex. The issue is fixed in version 6.2.4 (commit 18fd12efa98a7d1977de7bdd379d8a848777b90f).

Risk Assessment

With an exposed radare2 HTTP server, an attacker may bypass sandbox restrictions and run commands, including spawning processes. The risk mainly affects environments with a publicly reachable /cmd endpoint.

Recommendation

Upgrade radare2 to version 6.2.4 or later. Additionally, restrict network access to the radare2 HTTP server and do not expose the /cmd endpoint to untrusted users.

Other vulnerabilities in radare2

See all
Original NVD description (English source)

A vulnerability was detected in radareorg radare2 6.2.0/6.2.2. This issue affects the function r_core_cmd_str_pipe in the library libr/core/rtr_http.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."

Vulnerability data from NVD (NIST) · CISA KEV · EPSS