CVE-2026-112077

MEDIUMPre-NVD 5.65.6
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.6 from GitHub Security Advisory published 2026-10-19. A secondary CVSS source baseline 5.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
5.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

CVSS v3
5.6
EG Score
5.6MEDIUMhigh confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity56% × 45%
Impact severity (EG Severity): CVSS 5.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.6): severity, escalated by confirmed exploitation. This CVE's 5.6 is its impact severity (EG Severity), not escalated.

EG Severity
5.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 19, 2026

Last Modified

October 22, 2026

Advisory Details (4)

Auto-updated Oct 19, 2026
Patch available. Sources: github_release, github_commit.
Web page

GitHub - radareorg/radare2: UNIX-like reverse engineering framework and command-line toolset · GitHub

https://github.com/radareorg/radare2/
GitHub release Patch Available

6.2.4

Patch available: radareorg/radare2 6.2.4

https://github.com/radareorg/radare2/releases/tag/6.2.4
GitHub commit

commit 18fd12efa98a (radareorg/radare2)

Fix landed in radareorg/radare2 commit 18fd12efa98a — awaiting tagged release

https://github.com/radareorg/radare2/commit/18fd12efa98a7d1977de7bdd379d8a848777b90f
Web page

[Security]Potential inconsistency in HTTP sandbox enforcement in radare2 6.2.2 · Issue #26861 · radareorg/radare2 · GitHub

https://github.com/radareorg/radare2/issues/26861

Vendor Advisories for CVE-2026-112077(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-22 03:26 UTCEG score recompute
  4. 2026-10-22 03:26 UTCGHSA enrichmentGHSA-x2f6-pg54-586w · GitHub CVSS 5.6
  5. 2026-10-22 02:52 UTCEG score recompute
  6. 2026-10-22 02:52 UTCGHSA enrichmentGHSA-x2f6-pg54-586w · GitHub CVSS 5.6
  7. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-19 15:26 UTCEG score recompute
  11. 2026-10-19 15:26 UTCGHSA enrichmentGHSA-x2f6-pg54-586w · GitHub CVSS 5.6
  12. 2026-10-19 05:26 UTCEG score recompute
  13. 2026-10-19 04:31 UTCEG score recomputeFirst assessed: 5.6 MEDIUM
  14. 2026-10-19 04:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-112077?
CVE-2026-112077 is a medium-severity vulnerability; its CVE record was published on October 19, 2026. A vulnerability was detected in radareorg radare2 6.2.0/6.2.2. This issue affects the function rcorecmdstrpipe 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…
When was the CVE record for CVE-2026-112077 published?
The CVE record for CVE-2026-112077 was published on October 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-112077 actively exploited?
CVE-2026-112077 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-112077?
CVE-2026-112077 has a CVSS base score of 5.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-112077?
A fix for CVE-2026-112077 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-112077 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-112077

Explore →

Is Your Infrastructure Affected by CVE-2026-112077?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs