Remote process crash via double-free cleanup
Published May 15, 2026 · Updated May 15, 2026
Use-after-free in the GDB client core of radareorg radare2 6.1.5 allows remote attackers to crash the process via malformed thread replies. The gdbr_pids_list() cleanup path frees the last RDebugPid twice because dpid remains non-null after the object is appended to the list. The attacker must control the GDB server response so qfThreadInfo allocates an entry and qsThreadInfo fails; the published proof of concept demonstrates a process crash.
Summary
What happened
Use-after-free in the GDB client core of radareorg radare2 6.1.5 allows remote attackers to crash the process via malformed thread replies. The gdbr_pids_list() cleanup path frees the last RDebugPid twice because dpid remains non-null after the object is appended to the list. The attacker must control the GDB server response so qfThreadInfo allocates an entry and qsThreadInfo fails; the published proof of concept demonstrates a process crash.
The record
- CVE
- CVE-2026-8696
- Published
- May 15, 2026
- Updated
- May 15, 2026
- Vendor
- radareorg
- Product
- radare2
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- May 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=6.1.5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- uaf3.py malformed GDB server proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo