# CVE-2026-112077: radare2 sandbox policy enforcement bypass in HTTP handler

Source: https://junglewise.ai/threats/cve-2026-112077-a-vulnerability-was-detected-in-radareorg-radare2-6-2-0-6-2-2  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-19. Updated: 2026-10-19  
License: CC BY 4.0 with a link back

CVE-2026-112077 · Severity: medium · CVSS 5.6 · Published 2026-10-19

radare2 is a reverse-engineering framework that includes an HTTP server for remote command execution. When the HTTP sandbox is enabled, process execution was not properly restricted despite sandbox mode being active. An attacker with access to the exposed HTTP server could execute arbitrary commands on the system, bypassing the intended sandbox protections.

Technologies: [Radareorg Radare2](https://junglewise.ai/threats/technologies/radareorg-radare2). Vendors: [Radareorg](https://junglewise.ai/threats/vendors/radareorg).

## Quick answers

**Is CVE-2026-112077 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-112077 being exploited in the wild.

**How severe is CVE-2026-112077?** Medium severity, with a CVSS score of 5.6, published 19 October 2026.

**Which products and versions are affected?** Radareorg Radare2 6.2.0, 6.2.2.

**Is there a fix for CVE-2026-112077?** Yes: fixed in 6.2.4. Until then: Do not expose the HTTP server to untrusted networks. Restrict network access to the HTTP endpoint to trusted hosts only, or disable the HTTP server if it is not needed. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-112077 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-112077?** Check whether you run Radareorg Radare2 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 6.2.4

Do not expose the HTTP server to untrusted networks. Restrict network access to the HTTP endpoint to trusted hosts only, or disable the HTTP server if it is not needed.

## Technical details

The vulnerability is a protection mechanism failure in the r_core_cmd_str_pipe function within libr/core/rtr_http.inc.c. The HTTP sandbox could be bypassed because sandbox.grain defaults to "all", allowing execution capabilities even when http.sandbox=true. The issue requires the HTTP server to be started and exposed to an untrusted attacker; it is not remotely exploitable by default but becomes critical when the HTTP endpoint is accessible.

## Affected products

- radareorg radare2 6.2.0, 6.2.2

## Timeline

- 2026-10-19: disclosed
- 2026-10-01: patched: Commit 18fd12efa98a7d1977de7bdd379d8a848777b90f

## References

- [https://github.com/radareorg/radare2/](https://github.com/radareorg/radare2/)
- [https://github.com/radareorg/radare2/commit/18fd12efa98a7d1977de7bdd379d8a848777b90f](https://github.com/radareorg/radare2/commit/18fd12efa98a7d1977de7bdd379d8a848777b90f)

## Related threats

- [radare2 unbounded allocation in dmp64 parser](https://junglewise.ai/threats/cve-2026-81886-radare2-is-a-unix-like-reverse-engineering-framework-and-command)
- [radare2 heap out-of-bounds read in ELF PN_XNUM handling](https://junglewise.ai/threats/cve-2026-81879-radare2-is-a-unix-like-reverse-engineering-framework-and-command)