CVE-2026-81879

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2's ELF PN_XNUM handling was vulnerable because the ELF parser allocated the program-header array using the resolved PN_XNUM count but several consumers still iterated with the original e_phnum value of 65535. The vulnerability is triggered by processing a crafted ELF file with e_phnum = 0xffff and a much smaller resolved count in shdr[0].sh_info. Consumers iterated beyond the allocated program-header array. This can cause a heap out-of-bounds read and process termination, resulting in denial of service; memory disclosure and code execution have not been demonstrated. This issue is fixed in version 6.2.0.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

September 22, 2026

Last Modified

September 23, 2026

Advisory Details (5)

Auto-updated Sep 22, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

6.2.0

Patch available: radareorg/radare2 6.2.0

https://github.com/radareorg/radare2/releases/tag/6.2.0
github_commit

commit 9449b07579c1 (radareorg/radare2)

Fix landed in radareorg/radare2 commit 9449b07579c1 — awaiting tagged release

https://github.com/radareorg/radare2/commit/9449b07579c19b6b187c1a0918fbec2cef1a036e
github_pr

t pusj

Fix merged in radareorg/radare2 PR #26178 on 2026-07-06 — awaiting tagged release

https://github.com/radareorg/radare2/pull/26178
generic🟡 PoC Available

[Security] Heap out-of-bounds read in ELF parser via PN_XNUM program-header count desync · Issue #26223 · radareorg/radare2 · GitHub

https://github.com/radareorg/radare2/issues/26223
github Patch Available

Heap out-of-bounds read in radare2 ELF PN_XNUM handling · Advisory · radareorg/radare2 · GitHub

https://github.com/radareorg/radare2/security/advisories/GHSA-jqfq-hvcp-xh4p

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-24 19:43 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-23 18:26 UTCEG score recompute
  4. 2026-09-23 17:54 UTCEPSS rescore
  5. 2026-09-22 16:20 UTCEG score recompute
  6. 2026-09-22 15:45 UTCEG score recompute
  7. 2026-09-22 15:20 UTCEG score recompute
  8. 2026-09-22 15:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81879?
CVE-2026-81879 is a medium vulnerability published on September 22, 2026. radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2's ELF PNXNUM handling was vulnerable because the ELF parser allocated the program-header array using the resolved PNXNUM count but several consumers still iterated with the original ephnum value…
When was CVE-2026-81879 disclosed?
CVE-2026-81879 was first published in the National Vulnerability Database on September 22, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81879 actively exploited?
CVE-2026-81879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.1% of all scored CVEs.
What is the CVSS score of CVE-2026-81879?
CVE-2026-81879 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-81879?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81879, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-81879?

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