CVE-2025-5643VulnerabilityPublished 5 Jun 2025

CVE-2025-5643: Radare2 · Memory Corruption

Affects Radare2Source CVE Database V5

Not known to be exploited · CVSS 2.0 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

2.0Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubradareorg/radare2`pkg:github/radareorg/radare2`Other threats	Affected =5.9.9	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations using Radare2 5.9.9 should apply the official patch identified by commit 5705d99cc1f23f36f9a84aab26d1724010b97798 as soon as possible. Avoid using the experimental -T argument in radiff2 unless absolutely necessary, as it is known to be unstable and the root cause of this issue. Implement strict access controls to limit local access to systems running Radare2, reducing the attack surface. Employ monitoring to detect unusual local activity involving Radare2 usage. For environments using AddressSanitizer (ASAN), extra caution is advised since race conditions may be more problematic. Regularly update Radare2 to the latest stable versions to benefit from ongoing security improvements. Additionally, educate users about the risks of using experimental features and encourage adherence to best practices when handling security tools.

Description

A vulnerability classified as problematic was found in Radare2 5.9.9. Affected by this vulnerability is the function cons_stack_load in the library /libr/cons/cons.c of the component radiff2. The manipulation of the argument -T leads to memory corruption. An attack has to be approached locally. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The patch is named 5705d99cc1f23f36f9a84aab26d1724010b97798. It is recommended to apply a patch to fix this issue. The documentation explains that the parameter -T is experimental and "crashy". Further analysis has shown "the race is not a real problem unless you use asan". A new warning has been added.

Impact

For European organizations, the impact of this vulnerability is limited due to several factors. Radare2 is a reverse engineering framework primarily used by security researchers, malware analysts, and developers rather than general enterprise applications. The requirement for local access and the high complexity of exploitation reduce the risk of widespread attacks. The vulnerability does not compromise critical security properties such as confidentiality or integrity in a meaningful way, nor does it lead to denial of service or system-wide compromise. However, organizations relying on Radare2 for security analysis or development should be aware that exploitation could lead to application crashes or unstable behavior, potentially disrupting workflows. Since the vulnerability is tied to an experimental feature (-T argument), typical usage scenarios may not trigger the issue. Nonetheless, the presence of a public exploit disclosure means that targeted attackers with local access could attempt exploitation, emphasizing the need for patching in sensitive environments.

Summary

CVE-2025-5643 is a memory corruption vulnerability identified in Radare2 version 5.9.9, specifically within the function cons_stack_load located in the /libr/cons/cons.c source file of the radiff2 component. The vulnerability arises from improper handling of the -T argument, which is documented as experimental and prone to crashes. When this argument is manipulated, it can lead to memory corruption. Exploitation requires local access to the system and is considered complex and difficult, with no user interaction needed but requiring low privileges. The vulnerability does not affect confidentiality, integrity, or availability in a significant manner, as indicated by its low CVSS score of 2.0 (CVSS 4.0 vector: AV:L/AC:H/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N). The exploit has been publicly disclosed, but its practical existence is questioned, and no known exploits are currently observed in the wild. A patch identified by commit 5705d99cc1f23f36f9a84aab26d1724010b97798 has been released to address this issue. Additional analysis notes that race conditions related to this vulnerability are not a concern unless AddressSanitizer (ASAN) is used. A warning has been added to the software to highlight the experimental and unstable nature of the -T parameter.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 03:27 UTC

Technical details

References

Community reviews

Related threats