CVE-2026-14788
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 · uneditedA security vulnerability has been detected in radareorg radare2 up to 6.1.6. Affected by this vulnerability is the function r_core_bin_load of the file libr/core/cfile.c. Such manipulation leads to use after free. The attack needs to be performed locally. The exploit has been disclosed publicly and may be used. The name of the patch is 635ab1eeb30340c26076722a90cb91fb2272130b. Applying a patch is advised to resolve this issue.
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 · moderate confidenceA use-after-free vulnerability exists in the r_core_bin_load function in libr/core/cfile.c of radare2 up to version 6.1.6. An attacker with local access can manipulate memory after it has been freed, potentially leading to arbitrary code execution or denial of service.
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.0, <= 6.1.6CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify radare2 is installedRun 'r2 -v' or 'which r2' to confirm radare2 is present on the systemAffected if The command fails or r2 is not found, then radare2 is not installed and this CVE does not apply
-
Determine installed radare2 versionRun 'r2 -v' and note the version number returned (e.g., 6.1.6, 6.1.5, etc.)Affected if The version falls within 6.1.0 through 6.1.6 inclusive, meaning the installation is affected
-
Confirm core library presenceCheck for the existence of libr_core shared library (typically in /usr/lib or /usr/local/lib) or the cfile.c source file in the libr/core/ directoryAffected if The core library from a vulnerable version is present on the system
-
Check binary loading usageInspect recent commands or scripts that invoke r2, rabin2, or radare2 to load binary files (using commands like 'r2 -c "./bin"' or 'rabin2 -r')Affected if The tool is used to load or analyze binary files, which triggers the vulnerable r_core_bin_load function
The system is affected if radare2 is installed with a version between 6.1.0 and 6.1.6 inclusive and is used to load binary files.
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 · scopedApply the patch (commit 635ab1eeb30340c26076722a90cb91fb2272130b) or upgrade to a version beyond 6.1.6 that contains the fix. Given the public exploit availability and CVSS 7.8, prioritize remediation promptly.
- Identify the affected file: libr/core/cfile.c in the radare2 source tree
- Obtain the patch from commit 635ab1eeb30340c26076722a90cb91fb2272130b
- Apply the patch to the local radare2 repository using git am or by manually applying the diff
- Rebuild radare2 from the patched source code using ./configure && make
- Verify the patch was applied correctly by checking the r_core_bin_load function in libr/core/cfile.c
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14788 — 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-14788 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