# CVE-2026-8695: radare2 6.1.5 Use-After-Free via gdbr_threads_list()

> Remote attackers can trigger memory corruption in radare2 via GDB remote debugging, leading to denial of service or potential code execution.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-jrmh-3vm7-w5m4, UBUNTU-CVE-2026-8695, openSUSE-SU-2026:10815-1

## What is CVE-2026-8695?

CVE-2026-8695 is a high-severity use after free vulnerability in Radare Radare2, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

radare2 6.1.5 contains a use-after-free vulnerability in the gdbr_threads_list() function that allows remote attackers to trigger memory corruption by sending a valid qfThreadInfo response followed by a malformed qsThreadInfo response. Attackers can exploit this vulnerability through GDB remote debugging to cause a denial of service or potentially achieve code execution by manipulating thread list processing.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-8695?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `radare2` | openSUSE:Tumbleweed | All versions | 6.1.4-2.1 |

Products: Radare Radare2.

## How do I fix CVE-2026-8695?

Apply the vendor's patch.

## Is CVE-2026-8695 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8695 exists.

## Other vulnerabilities in Radare Radare2

- [CVE-2025-1864](https://insights.sbomify.com/CVE-2025-1864/): Buffer Overflow and Potential Code Execution in Radare2 (critical 10.0)
- [CVE-2025-1744](https://insights.sbomify.com/CVE-2025-1744/): Out-of-bounds Write in radare2 (critical 10.0)
- [CVE-2021-32494](https://insights.sbomify.com/CVE-2021-32494/): Denial of service in radare2 (critical 10.0)
- [CVE-2021-32495](https://insights.sbomify.com/CVE-2021-32495/): Use after free in radare2 (critical 10.0)
- [CVE-2024-29646](https://insights.sbomify.com/CVE-2024-29646/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8695 and fix it if it is affected.

What it is: CVE-2026-8695 is a high-severity use after free vulnerability in Radare Radare2, published on 15 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8695 exists.

Affected product: Radare Radare2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8695/ (Markdown: https://insights.sbomify.com/CVE-2026-8695/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8695
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8695
- OSV: https://osv.dev/vulnerability/CVE-2026-8695

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8695/
Summaries are generated and may contain mistakes; the official description above is the record.