CVE-2026-81886: radare2: Uncontrolled memory allocation in radare2 dmp64 parser

Published Sep 22, 2026
·
Updated

radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2's Windows 64-bit crash-dump dmp64 parser was vulnerable because the Windows dmp64 parser used an input-controlled physical-memory-run PageCount directly as the bound of a per-page allocation loop. The vulnerability is triggered by opening a small crafted full-memory Windows crash dump. The parser repeatedly allocated and appended page descriptors without validating the count against the dump size. This can cause denial of service through excessive memory consumption and processing time. This issue is fixed in version 6.2.0.

Affected Software

1 affected component
radareorg radare2<6.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade radare2 to a version that resolves this vulnerability.

    Fixed in 6.2.0

Event History

Sep 22, 2026
CVE Published
via MITRE·03:11 PM
Data Sourced
via MITRE·03:11 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Users running radare2 versions before 6.2.0 who open Windows 64-bit full-memory crash dumps are exposed. The affected component is the dmp64 parser.

2

What must an attacker do to trigger the denial of service?

An attacker must provide a small crafted full-memory Windows crash dump and have it opened by radare2. No privileges are required, but user interaction is required to open the malicious dump.

3

Are normal crash dumps affected?

The available information identifies crafted full-memory Windows crash dumps as the trigger. It does not state that other dump types or ordinary crash dumps are affected.

4

What should be done if immediate patching is not possible?

Avoid opening untrusted or unvalidated Windows 64-bit full-memory crash dumps with affected radare2 versions. The described impact is excessive memory consumption and processing time.

5

How can I determine whether my installation is affected?

Check the radare2 version in use. Versions prior to 6.2.0 are affected; version 6.2.0 contains the fix.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203