← Back to results
Vulnerability record · public intelligence
CVE-2026-81884
LOW

radare2: Heap out-of-bounds read in radare2 Mach-O LC_DATA_IN_CODE parser

Published Sep 22, 2026 · Updated Oct 23, 2026

Severity · CVSSLOW · 2.5
Known exploitationNot listed
EPSS / likelihood0.15%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

radare2: Heap out-of-bounds read in radare2 Mach-O LC_DATA_IN_CODE parser

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2's Mach-O LC_DATA_IN_CODE parser was vulnerable because the Mach-O LC_DATA_IN_CODE parser trusted dataoff and datasize and allowed a final partial record to be processed. The vulnerability is triggered by opening a crafted Mach-O file while the non-default bin.verbose option is enabled. When datasize was not a multiple of data_in_code_entry, the last iteration read beyond the allocated buffer. This can cause a heap out-of-bounds read and possible process termination; no attacker-observable memory disclosure has been demonstrated. This issue is fixed in version 6.2.0.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Source repository ↗
  3. Source repository ↗
  4. Patch commit ↗
  5. Source repository ↗

Record history

Published Sep 22, 2026 · Last refreshed Oct 23, 2026