CVE-2026-8695: radare2 · Use After Free
Affects radare2Source GCVE Database
Not known to be exploited · CVSS 8.7 High.
Data as of 11 Nov 2026, 23:07 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.5 |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 15 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 11 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| radare2 radare2 | Affected
| Fixed in– |
AI-suggested
Users should monitor vendor advisories for updates. Until a fix is released, avoid exposing radare2's GDB remote debugging interface to untrusted networks to reduce the risk of exploitation.
Description
radare2 version 6.1.5 contains a use-after-free vulnerability in the gdbr_threads_list() function. This flaw can be triggered remotely via GDB remote debugging by sending a valid qfThreadInfo response followed by a malformed qsThreadInfo response. Exploitation may lead to denial of service or potentially code execution by corrupting memory during thread list processing.
References
- github.com/radareorg/radare2/issues/25835 (opens in a new tab)
- github.com/radareorg/radare2/commit/c213ad6894a1eb9086ac8bf5fae35757e9e1683c (opens in a new tab)
- vulncheck.com/advisories/radare2-use-after-free-via-gdbr-threads-list (opens in a new tab)
- github.com/radareorg/radare2/issues/25836 (opens in a new tab)