CVE-2026-8696: radare2 6.1.5 Use-After-Free via gdbr_pids_list()
radare2 6.1.5 contains a use-after-free vulnerability in the gdbr_pids_list() function within the GDB client core that allows remote attackers to cause a denial of service or potentially execute arbitrary code by sending malformed thread information responses. Attackers can trigger the vulnerability by causing qsThreadInfo to fail after qfThreadInfo successfully allocates RDebugPid structures, resulting in double-free memory corruption when the error path attempts to clean up the list.
Security readout for executives and security teams
Plain-English summary
Radare2 6.1.5 can mishandle malformed thread information from a remote GDB debugging endpoint. A malicious or compromised endpoint could crash the tool and may enable arbitrary code execution. This primarily affects teams using radare2 for reverse engineering, malware analysis, or remote debugging against untrusted targets.
Executive priority
Treat as high priority for security research and malware-analysis environments. The broad enterprise blast radius is probably limited, but affected analyst systems often handle untrusted inputs and may have sensitive tooling or samples nearby.
Technical view
The vulnerability is a CWE-416 use-after-free in gdbr_pids_list() in the GDB client core. If qfThreadInfo allocates RDebugPid structures and qsThreadInfo then fails, the cleanup path can double-free list state, causing memory corruption. CVSS v4.0 is 8.7 with network attack vector and no required privileges or user interaction.
Likely exposure
Exposure is likely limited to systems running radare2 6.1.5, especially analyst workstations, research VMs, CI images, or services that connect radare2's GDB client to remote or untrusted debugging endpoints.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references describe malformed thread information responses as the trigger condition, but do not establish real-world exploitation in the provided evidence.
Researcher notes
Evidence supports a memory-safety flaw in the GDB client error path, with denial of service and potential code execution impact. The provided sources identify a patch reference, but release-level remediation details should be confirmed with radare2 upstream guidance.
Mitigation direction
Identify and prioritize radare2 6.1.5 deployments.
Review the upstream issue and patch commit for vendor remediation guidance.
Upgrade to a vendor release that includes the referenced fix when available.
Avoid connecting radare2 GDB client sessions to untrusted remote endpoints.
Run radare2 analysis in isolated research environments.
Validation and detection
Inventory installed radare2 versions across workstations, containers, and analysis environments.
Check whether affected builds include version 6.1.5 or the referenced affected commit.
Review workflows that use radare2 remote GDB client functionality.
Confirm remediation against the upstream issue and patch reference.
Monitor vendor and CVE records for updated affected-version guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.