CVE-2025-5646VulnerabilityPublished 5 Jun 2025

CVE-2025-5646: Radare2 · Memory Corruption

Affects Radare2Source CVE Database V5

Not known to be exploited · CVSS 2.0 Low.

Data as of 25 Oct 2026, 19:02 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 2026-10-25.

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

Organizations using Radare2 should update to a patched version that includes the fix identified by commit 5705d99cc1f23f36f9a84aab26d1724010b97798. Users should avoid using the experimental -T parameter until the patch is applied, as it is the root cause of the memory corruption. Additionally, restricting Radare2 usage to trusted users and environments can minimize the risk of local exploitation. Implementing strict access controls and monitoring for unusual local activity related to Radare2 can further reduce exposure. Security teams should also educate users about the risks of using experimental features in security tools and encourage adherence to stable releases. Regularly reviewing and updating reverse engineering tools as part of vulnerability management processes is recommended.

Description

A vulnerability has been found in Radare2 5.9.9 and classified as problematic. This vulnerability affects the function r_cons_rainbow_free in the library /libr/cons/pal.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 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 identified as 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 CVE-2025-5646 is minimal due to several factors. Radare2 is primarily a tool used by security researchers, reverse engineers, and developers rather than a core component of enterprise infrastructure. The vulnerability requires local access and the use of an experimental feature, limiting the attack surface. Consequently, it is unlikely to be exploited in large-scale attacks or cause significant disruption. However, organizations that rely on Radare2 for security assessments or malware analysis should be aware of this vulnerability to avoid potential crashes or instability during their workflows. The low severity and lack of known exploits reduce the urgency, but patching remains advisable to maintain tool reliability and security hygiene.

Summary

CVE-2025-5646 is a memory corruption vulnerability identified in Radare2 version 5.9.9, specifically within the function r_cons_rainbow_free located in the /libr/cons/pal.c component of radiff2. The vulnerability arises from improper handling of the -T argument, which is documented as experimental and prone to causing crashes. Exploitation involves manipulating this argument to trigger memory corruption. The attack vector is local, requiring the attacker to have access to the host system. The complexity of exploitation is considered high, and the exploit is difficult to execute reliably. Additionally, the vulnerability's real-world existence has been questioned, and no known exploits are currently active in the wild. A patch has been committed (identified by commit 5705d99cc1f23f36f9a84aab26d1724010b97798) to address this issue. The vulnerability does not require user interaction or network access, and it does not escalate privileges or affect confidentiality, integrity, or availability significantly. The CVSS 4.0 score is 2, reflecting a low severity rating. The vulnerability is mainly relevant to users who utilize the experimental -T parameter in Radare2, a reverse engineering framework commonly used for binary analysis and debugging.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats