Skip to main content
VulnerabilityPublished Updated

CVE-2026-8695: radare2 · Use After Free

Affects radare2Source GCVE Database

0
Compare

Not known to be exploited · CVSS 8.7 High.

Data as of 11 Nov 2026, 23:07 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.17.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
radare2 radare2Affected
  • =6.1.5
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

Community reviews

Loading reviews…