VulnerabilityPublished 5 Jun 2025

CVE-2025-5641: Radare2 · Memory Corruption

Affects Radare2Source CVE Database V5

Not known to be exploited · CVSS 2.0 Low.

Data as of 26 Oct 2026, 09:15 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 13% 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 26 Oct 2026.

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

1. Immediate application of the official patch identified by commit 5705d99cc1f23f36f9a84aab26d1724010b97798 to Radare2 version 5.9.9 is strongly recommended to eliminate the vulnerability. 2. Avoid using the experimental -T parameter in Radare2 until the patch is applied and the feature is deemed stable. 3. Restrict local access to systems running Radare2 to trusted users only, employing strict access controls and monitoring to prevent unauthorized local exploitation attempts. 4. Implement host-based intrusion detection systems (HIDS) to detect anomalous behavior or crashes related to Radare2 processes. 5. Conduct regular audits of installed software versions and configurations to ensure no vulnerable Radare2 instances are in use. 6. Educate security analysts and researchers about the risks associated with experimental features and encourage the use of stable releases in production or sensitive environments. 7. If AddressSanitizer is used in testing or development environments, be aware of the threading warnings and potential race conditions to avoid false positives or overlooked issues.

Description

A vulnerability was found in Radare2 5.9.9. It has been rated as problematic. This issue affects the function r_cons_is_breaked in the library /libr/cons/cons.c of the component radiff2. The manipulation of the argument -T leads to memory corruption. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation is known 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 identifier of the patch is 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". An additional warning regarding threading support has been added.

Impact

For European organizations, the impact of CVE-2025-5641 is generally low due to several factors: the vulnerability requires local access and low privileges, making remote exploitation infeasible; the attack complexity is high, reducing the likelihood of successful exploitation; and the affected feature (-T parameter) is experimental and not commonly used in production settings. However, organizations that use Radare2 extensively for reverse engineering, malware analysis, or security research could face risks if untrusted users gain local access to systems running the vulnerable version. Memory corruption could potentially lead to application crashes or limited code execution scenarios, which might disrupt analysis workflows or lead to denial of service in sensitive environments. Since Radare2 is popular among security professionals and researchers, the vulnerability could be leveraged in targeted attacks within organizations that rely on this tool, especially if combined with other vulnerabilities or insider threats. Overall, the direct impact on confidentiality, integrity, and availability is limited but should not be ignored in high-security or research environments.

Summary

CVE-2025-5641 is a memory corruption vulnerability identified in Radare2 version 5.9.9, specifically within the function r_cons_is_breaked located in the radiff2 component's /libr/cons/cons.c file. The vulnerability arises from improper handling of the experimental -T argument, which can lead to memory corruption when manipulated. Radare2 is an open-source reverse engineering framework widely used for binary analysis and debugging. The vulnerability requires local access to the host to be exploited, and the attack complexity is considered high, with exploitation known to be difficult. The vulnerability does not require user interaction but does require low-level privileges (local privileges) to execute. The issue is compounded by threading concerns, although the race condition is not considered a significant problem unless AddressSanitizer (ASAN) is used. A patch identified by commit 5705d99cc1f23f36f9a84aab26d1724010b97798 has been released to address this issue. Despite public disclosure of the exploit, the real-world existence and impact of this vulnerability remain somewhat uncertain. The CVSS v4.0 score is low (2.0), reflecting limited impact and high attack complexity. The vulnerability affects only Radare2 version 5.9.9, and the -T parameter is marked as experimental and unstable, which may limit exposure in production environments.

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