radareorg radare2 up to 6.1.6 libr/core/cfile.c r_core_bin_load use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 1.14+ |
Summary
A vulnerability, which was classified as problematic, has been found in radareorg radare2 up to 6.1.6. Affected by this issue is the function r_core_bin_load of the file libr/core/cfile.c. Performing a manipulation results in use after free.
This vulnerability is reported as CVE-2026-14788. The attack requires a local approach. Moreover, an exploit is present.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in radareorg radare2 up to 6.1.6. It has been classified as problematic. This affects the function r_core_bin_load of the file libr/core/cfile.c. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-14788. The exploitability is told to be easy. An attack has to be approached locally. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept.
Applying the patch 635ab1eeb30340c26076722a90cb91fb2272130b is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 635ab1eeb30340c26076722a90cb91fb2272130b
Timeline
07/05/2026 Advisory disclosed07/05/2026 VulDB entry created
07/05/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 26049
Status: Confirmed
CVE: CVE-2026-14788 (🔒)
GCVE (CVE): GCVE-0-2026-14788
GCVE (VulDB): GCVE-100-376377
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/05/2026 18:08Changes: 07/05/2026 18:08 (60)
Complete: 🔍
Submitter: Kery Qi
Cache ID: 216::103
Submit
Accepted
- Submit #850388: radareorg radare2 6.1.6 Use After Free (by Kery Qi)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.