radareorg radare2 up to 6.1.6 regprofile libr/core/disasm.c r_core_seek_arch_bits use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.0$0-$5k1.35+

Summaryinfo

A vulnerability, which was classified as problematic, has been found in radareorg radare2 up to 6.1.6. The affected element is the function r_core_seek_arch_bits of the file libr/core/disasm.c of the component regprofile Handler. The manipulation leads to use after free. This vulnerability is traded as CVE-2026-14760. An attack has to be approached locally. Furthermore, there is an exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in radareorg radare2 up to 6.1.6 and classified as problematic. This issue affects the function r_core_seek_arch_bits of the file libr/core/disasm.c of the component regprofile Handler. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is availability.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-14760. The exploitation is known to be easy. An attack has to be approached locally. Technical details as well as a public exploit are known.

The exploit is available at github.com. It is declared as proof-of-concept.

Applying the patch 8b25c773785d85cb0103410a0905089d286921c2 is able to eliminate this problem. The bugfix is ready for download at github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

0-Day Time: 🔒

Patch: 8b25c773785d85cb0103410a0905089d286921c2

Timelineinfo

07/04/2026 Advisory disclosed
07/04/2026 +0 days VulDB entry created
07/04/2026 +0 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: 26044
Status: Confirmed

CVE: CVE-2026-14760 (🔒)
GCVE (CVE): GCVE-0-2026-14760
GCVE (VulDB): GCVE-100-376349
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 07/04/2026 18:24
Changes: 07/04/2026 18:24 (61)
Complete: 🔍
Submitter: Kery Qi
Cache ID: 216::103

Submitinfo

Accepted

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!