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.
CVE-2026-81879
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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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 computedSeverity55% × 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, 20266.2.0
Patch available: radareorg/radare2 6.2.0
https://github.com/radareorg/radare2/releases/tag/6.2.0commit 9449b07579c1 (radareorg/radare2)
Fix landed in radareorg/radare2 commit 9449b07579c1 — awaiting tagged release
https://github.com/radareorg/radare2/commit/9449b07579c19b6b187c1a0918fbec2cef1a036et pusj
Fix merged in radareorg/radare2 PR #26178 on 2026-07-06 — awaiting tagged release
https://github.com/radareorg/radare2/pull/26178[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/26223Heap out-of-bounds read in radare2 ELF PN_XNUM handling · Advisory · radareorg/radare2 · GitHub
https://github.com/radareorg/radare2/security/advisories/GHSA-jqfq-hvcp-xh4pWeakness 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.
- 2026-09-24 19:43 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 18:26 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 16:20 UTCEG score recompute
- 2026-09-22 15:45 UTCEG score recompute
- 2026-09-22 15:20 UTCEG score recompute
- 2026-09-22 15:19 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-81879?
When was CVE-2026-81879 disclosed?
Is CVE-2026-81879 actively exploited?
What is the CVSS score of CVE-2026-81879?
How do I remediate CVE-2026-81879?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81879
Is Your Infrastructure Affected by CVE-2026-81879?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.