CVE Intelligence
Medium

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

Published Oct 19, 2026 · Updated Oct 22, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.29%
ahead of 20% of scored CVEs · Oct 21, 2026
Affects
Radareorg
Radare2
CVSS base
5.6
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Radareorg Radare2).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Radareorg Radare2 version 6.2.0version 6.2.2 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
6.3 CVSS 4.0 Medium — — cna@vuldb.com via NIST National Vulnerability Database
6.3 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.6 CVSS 3.1 Medium 2.2 3.4 cna@vuldb.com via NIST National Vulnerability Database
5.6 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.6 CVSS 3.1 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.6 CVSS 3.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.1 CVSS 2.0 Medium 4.9 6.4 cna@vuldb.com via NIST National Vulnerability Database
5.1 CVSS 2.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-693

Other CVEs with this weakness →

EPSS over time FIRST

Oct 19, 2026 → Oct 21, 2026 · 3 reading(s) · max 0.29%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Received → Deferred
    Oct 19, 2026 · NIST National Vulnerability Database
  • Affected products added · radareorg/radare2
    Oct 19, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 19, 2026
  • CVSS changed · 5.6
    Oct 19, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 19, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 19, 2026 · Alertas do Telegram
  • CVE published
    Oct 19, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 19, 2026 – Oct 22, 2026
  • 1× Official description updated · Oct 19, 2026 – Oct 19, 2026

References

11 on the record

Elsewhere on this site

Radareorg
every CVE for this vendor
CWE-693
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-81886 radare2: Uncontrolled memory allocation in radare2 dmp64 parser Sep 22, 2026
  • CVE-2026-81882 radare2: Missing string termination causes heap out-of-bounds read in radare2 bplist parser Sep 22, 2026
  • CVE-2026-81883 radare2: Out-of-bounds Read at the end of string in the LUA 5.3 bytecode Sep 22, 2026
  • CVE-2026-81885 radare2: Infinite relocation-chain loop causes denial of service in radare2 NE parser Sep 22, 2026
  • CVE-2026-81884 radare2: Heap out-of-bounds read in radare2 Mach-O LC_DATA_IN_CODE parser Sep 22, 2026
  • CVE-2026-81879 radare2: Heap out-of-bounds read in radare2 ELF PN_XNUM handling Sep 22, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-112077 is "radareorg radare2 HTTP Sandbox Policy rtr_http.inc.c r_core_cmd_str_pipe protection mechanism", rated Medium. It affects Radare2 (Radareorg); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.6 describes technical severity. EPSS 0.29% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.