Skip to main content
VulnerabilityPublished Updated

CVE-2026-81882: radareorg radare2 · Out-of-bounds Read

Affects radareorg radare2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.3 Low : upgrade to 6.2.0 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
3.3Low
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:L/I:N/A:N

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

This vulnerability is fixed in radare2 version 6.2.0. Users should upgrade to version 6.2.0 or later to remediate this issue. No other mitigation or workaround is indicated by the vendor advisory.

Description

CVE-2026-81882 is an out-of-bounds read vulnerability in radare2's binary property-list Unicode parser prior to version 6.2.0. The vulnerability occurs because the parser underallocates an uninitialized UTF-8 destination and does not guarantee NUL termination. Triggered by running the pFB or pFBj commands on untrusted binary property-list data, this causes the JSON encoder to read beyond the allocated buffer, potentially disclosing uninitialized or adjacent heap memory. The issue is fixed in radare2 version 6.2.0.

References

Community reviews

Loading reviews…