dbcve.org
Radare2Application · Radare

CVE-2026-8696

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-15
Fix available
A fix is available. Upgrade to after 6.1.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

radare2 6.1.5 has a use-after-free/double-free vulnerability in gdbr_pids_list() within the GDB client. When processing GDB remote protocol thread information, qfThreadInfo allocates RDebugPid structures successfully, but if qsThreadInfo subsequently fails, the error cleanup path attempts to double-free these structures, causing memory corruption that can lead to denial of service or arbitrary code execution.

MitigationUpgrade to the patched version of radare2 when released; until then, avoid using the GDB remote debugging client with untrusted remote targets, as the vulnerability is triggered by malformed thread info responses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Radare2Application
Affected:<= 6.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed radare2 version
    Run 'radare2 -v' or 'r2 -v' to display the version string
    Affected if Version is 6.1.4 or lower
  2. Confirm GDB remote protocol is in use
    Check if radare2 is being used with GDB remote debugging features, such as connecting to a remote GDB server via 'radare2 -g' or using the 'gdbr' commands
    Affected if GDB remote protocol functionality is actively used or configured to connect to remote GDB servers
  3. Inspect process memory behavior
    While debugging with radare2's GDB remote client, monitor for crashes or memory corruption in the gdbr_pids_list code path when thread enumeration fails
    Affected if Crashes or memory corruption occur during remote GDB thread info queries

A system is affected if radare2 version 6.1.4 or lower is installed AND the GDB remote protocol client functionality is being used to connect to remote GDB servers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 6.1.4
Vendor patch github.com →
Interim mitigation

Upgrade to the patched version of radare2 when released; until then, avoid using the GDB remote debugging client with untrusted remote targets, as the vulnerability is triggered by malformed thread info responses.

Recommended fix High confidence

radare2 version 6.1.5 or later

  1. 1. Ensure you have a backup of your current radare2 installation and any projects using it
  2. 2. Update radare2 to version 6.1.5 or later using your package manager or build from source
  3. 3. If using package managers: run 'apt-get update && apt-get upgrade radare2' (Debian/Ubuntu) or equivalent for your distribution
  4. 4. If building from source: clone the repository and run './configure && make && make install' to get the latest version
  5. 5. Verify the installation by running 'r2 -v' to confirm the version is 6.1.5 or higher
  6. 6. Test your workflows that use the GDB remote debugging functionality to ensure the fix is effective

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Radare2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8696 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8696 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data