CVE-2026-8695
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 · uneditedradare2 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.
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 confidenceradare2 6.1.5 has a use-after-free vulnerability in gdbr_threads_list() that allows memory corruption via the GDB remote debugging protocol. The issue is triggered by sending a valid qfThreadInfo response followed by a malformed qsThreadInfo response, causing the program to access freed memory during thread list processing.
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<= 6.1.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check radare2 versionRun 'r2 -v' or 'radare2 -v' to display the installed versionAffected if The version displayed is 6.1.4 or lower (including any 6.0.x, 5.x.x versions)
-
Verify GDB remote debugging is enabledConfirm that radare2 is being used with GDB remote protocol support - this is typically invoked with 'r2 -g' or when connecting to remote GDB targets using the 'gdb' io pluginAffected if GDB remote debugging functionality is actively used or configured in your radare2 environment
-
Identify active GDB remote sessionsReview any active debug sessions or logs that show GDB protocol communication (qfThreadInfo/qsThreadInfo packets) between radare2 and a remote targetAffected if GDB remote debugging sessions exist where untrusted or potentially malicious remote targets could send crafted protocol responses
You are affected if you run radare2 version 6.1.4 or lower AND use GDB remote debugging functionality to connect to remote targets.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to a patched version of radare2 when available; avoid connecting to untrusted GDB remote debugging targets until the vulnerability is resolved.
radare2 version 6.1.5 or later
- 1. Ensure you have the current vulnerable version of radare2 installed (verify with `radare2 -v` showing <= 6.1.4)
- 2. Update radare2 to the latest stable release by running: `git pull` in the radare2 source directory followed by `make` and `make install`
- 3. Alternatively, use the system's package manager to upgrade (e.g., `apt update && apt upgrade radare2` on Debian-based systems)
- 4. Verify the upgrade was successful by running `radare2 -v` and confirming the version is 6.1.5 or later
- 5. Test that the GDB remote debugging functionality works correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8695 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8695 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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