CVE-2026-81881

MEDIUMNVD 4.44.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.4 under NVD CVSS v3. EPSS exploit probability: 0.2% (5th 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

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

4.4EG
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.2%CVSS: 4.4Exploit: None knownExposed 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 Mach-O Swift field-metadata parser was vulnerable because a relative Swift field pointer could be lower than the field-metadata section base, making subtraction produce a negative logical index. The vulnerability is triggered by parsing Swift type and class metadata from a crafted Mach-O file. The derived index was used to read four bytes immediately before the allocated field-metadata buffer. This can cause incorrect metadata processing or process termination; no attacker-observable memory disclosure has been demonstrated. This issue is fixed in version 6.2.0.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/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)
Severity44% × 45%
Impact severity (EG Severity): CVSS 4.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.2%
EPSS %ILE
5th
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 (4.4): severity, escalated by confirmed exploitation. This CVE's 4.4 is its impact severity (EG Severity), not escalated.

EG Severity
4.4 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. 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, and whom BOD 26-04 binds: 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.

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 (4)

Auto-updated Sep 25, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Heap out-of-bounds read in radare2 Mach-O Swift metadata parser · Advisory · radareorg/radare2 · GitHub

https://github.com/radareorg/radare2/security/advisories/GHSA-q4w7-225g-64j9
GitHub release Patch Available

6.2.0

Patch available: radareorg/radare2 6.2.0

https://github.com/radareorg/radare2/releases/tag/6.2.0
Web page

[Security] Heap out-of-bounds read in Mach-O Swift field-metadata parser via negative index · Issue #26229 · radareorg/radare2 · GitHub

https://github.com/radareorg/radare2/issues/26229
GitHub commit

commit 1da6e782df22 (radareorg/radare2)

Fix landed in radareorg/radare2 commit 1da6e782df22 — awaiting tagged release

https://github.com/radareorg/radare2/commit/1da6e782df220edf56138ef5fe4f33745b04db74

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81881?
CVE-2026-81881 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 Mach-O Swift field-metadata parser was vulnerable because a relative Swift field pointer could be lower than the field-metadata section base, making subtraction produce a negative logical index.…
When was the CVE record for CVE-2026-81881 published?
The CVE record for CVE-2026-81881 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-81881 actively exploited?
CVE-2026-81881 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81881?
CVE-2026-81881 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-81881?
A fix for CVE-2026-81881 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-81881

Explore →

Is Your Infrastructure Affected by CVE-2026-81881?

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

Book a Demo →Browse All CVEs