CVE-2026-14757
Description
A flaw was found in radareorg radare2. A local attacker could exploit an integer overflow vulnerability within the core_anal_bytes function. This manipulation could lead to limited impacts on confidentiality, integrity, and availability of the system.
Statement
This Moderate impact flaw in radare2 allows a local attacker to trigger an integer overflow within the core_anal_bytes function. Exploitation requires local access to the system and could lead to limited impacts on data confidentiality, integrity, and system availability.
Mitigation
To mitigate this issue, users should exercise caution when processing untrusted or maliciously crafted files with radare2. Avoid opening or analyzing files from unknown or unverified sources. Additionally, consider running radare2 within a sandboxed environment, such as a container or a restricted user account, to further limit the potential impact of exploitation.
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (Memory); DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided.
Integrity
Technical Impact: Modify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality,Availability,Access Control
Technical Impact: Execute Unauthorized Code or Commands; Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability,Other
Technical Impact: Alter Execution Logic; DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading to a crash or other DoS.
Access Control
Technical Impact: Bypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
