Skip to main content
VulnerabilityPublished

CVE-2026-81886: radareorg radare2 · Unthrottled Resource Allocation

Affects radareorg radare2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium : upgrade to 6.2.0 when convenient.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.2.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade radare2 and radareorg/radare2 to 6.2.0.

Affected software

ProductAffectedFixed in
radareorgradare2Affected
  • <6.2.0
Fixed in
  • 6.2.0
GitHubradareorg/radare2pkg:github/radareorg/radare2Other threatsAffected
  • <6.2.0
Fixed in
  • 6.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade radare2 to version 6.2.0 or later, where this vulnerability has been fixed. No other specific mitigations are indicated.

Description

CVE-2026-81886 is a medium severity vulnerability in radare2 prior to version 6.2.0. It involves the Windows 64-bit crash-dump dmp64 parser, which improperly uses an input-controlled PageCount to allocate memory without validating against the dump size. This can lead to excessive memory consumption and processing time, causing a denial of service. The issue is fixed in radare2 version 6.2.0.

References

Community reviews

Loading reviews…