CVE-2026-81879

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-84504 (ENISA EUVD)Source: ENISA EUVD

6.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.2%
EPSS %ILE
7th
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 (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 low or medium mission impact; Track* at high (mission-essential systems).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, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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.

The score's inputs: 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

September 22, 2026

Last Modified

September 25, 2026

Advisory Details (5)

Auto-updated Sep 22, 2026
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 pull request

t pusj

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

https://github.com/radareorg/radare2/pull/26178
Web page

[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 advisoryMentions a patch (unverified)

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 / 45× 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-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-10-30 01:55 UTCOSV refresh
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-25 13:58 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-22 13:46 UTCEG score recompute
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-18 03:09 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 43 more
  1. 2026-10-12 14:56 UTCEG score recompute
  2. 2026-10-11 19:20 UTCEG score recompute
  3. 2026-10-11 16:36 UTCEG score recompute
  4. 2026-10-11 13:54 UTCEG score recompute
  5. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-10 14:05 UTCEG score recompute
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-09 12:48 UTCEG score recompute
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-08 10:47 UTCEG score recompute
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-07 09:19 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-06 08:01 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-05 06:46 UTCEG score recompute
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-04 05:30 UTCEG score recompute
  20. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-03 04:13 UTCEG score recompute
  22. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-02 02:57 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-01 01:35 UTCEG score recompute
  26. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-09-30 00:19 UTCEG score recompute
  28. 2026-09-28 20:59 UTCEG score recompute
  29. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-27 19:42 UTCEG score recompute
  31. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-26 18:26 UTCEG score recompute
  33. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-25 17:09 UTCEG score recompute▲ 0.60
  35. 2026-09-25 17:07 UTCNVD updateCVSS v3 → 6.1
  36. 2026-09-24 19:43 UTCEG score recompute
  37. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-23 18:26 UTCEG score recompute
  39. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-09-22 16:20 UTCEG score recompute
  41. 2026-09-22 15:45 UTCEG score recompute
  42. 2026-09-22 15:20 UTCEG score recomputeFirst assessed: 5.5 MEDIUM
  43. 2026-09-22 15:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81879?
CVE-2026-81879 is a medium-severity vulnerability; its CVE record was 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 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…
When was the CVE record for CVE-2026-81879 published?
The CVE record for CVE-2026-81879 was published on September 22, 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 September 25, 2026; the record at its source may have been updated since.
Is CVE-2026-81879 actively exploited?
CVE-2026-81879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81879?
CVE-2026-81879 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-81879?
A fix for CVE-2026-81879 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs