---
id: "CVE-2026-112077"
kind: "vulnerability"
aliases: ["CVE-2026-112077"]
title: "radare2: HTTP sandbox default lets remote /cmd requests run processes"
severity: "medium"
cvss: 6.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "radare2", "reverse-engineering", "self-hosted"]
not_affected_if: ["auth-required", "http-server-not-running", "localhost-only"]
published_at: "2026-10-19T05:17:04+00:00"
first_seen_at: "2026-10-23T21:57:17+00:00"
updated_at: "2026-10-25T04:01:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112077", "first_seen_at": "2026-10-23T21:57:17+00:00"}]
---

# radare2: HTTP sandbox default lets remote /cmd requests run processes

In radare2 6.2.0 and 6.2.2, the HTTP server's sandbox setting does not block command execution because the default sandbox grain still allows exec. A remote user who can reach the HTTP command endpoint can therefore spawn processes on the host.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- `r2 -v` to read the installed radare2 version and confirm it is `6.2.0` or `6.2.2`
- Check whether the HTTP server is started and reachable, for example by looking for `=h` or `-e http.port` in scripts or service files that run radare2 over HTTP
- Check whether the `/cmd` endpoint is exposed beyond trusted users

## Fix

- Upgrade radare2 to `6.2.4` or later (patch `18fd12efa98a7d1977de7bdd379d8a848777b90f`)
- Do not expose the radare2 HTTP server to untrusted networks until upgraded
- Until then, set the sandbox grain to deny exec, for example `e cfg.sandbox.grain=...` with exec removed, and restrict access to the HTTP port

## Timeline

- 2026-10-23T21:57:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-112077

## From the sources

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."

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_