Skip to main content
CVE-2025-5644VulnerabilityPublished

CVE-2025-5644: Radare2 · Use After Free

Affects Radare2Source CVE Database V5

0

Not known to be exploited · CVSS 2.0 Low.

Data as of 26 Oct 2026, 08:30 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubradareorg/radare2pkg:github/radareorg/radare2Other threatsAffected
  • =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

European organizations using Radare2 should take the following specific mitigation steps: 1) Immediately update Radare2 to a version that includes the patch identified by commit 5705d99cc1f23f36f9a84aab26d1724010b97798 or later, ensuring the vulnerability is remediated. 2) Avoid using the experimental -T parameter in radiff2 or any other Radare2 components until the patch is applied and the feature is deemed stable. 3) Implement strict access controls to limit local user access to systems running Radare2, reducing the risk of exploitation by unauthorized users. 4) Monitor internal security tools and workflows for crashes or abnormal behavior related to Radare2 usage, which could indicate attempts to trigger this vulnerability. 5) Educate security analysts and developers about the risks associated with experimental features and encourage cautious use of such parameters. These targeted actions go beyond generic advice by focusing on the specific vulnerable component and usage patterns.

Description

A vulnerability, which was classified as problematic, has been found in Radare2 5.9.9. Affected by this issue is the function r_cons_flush in the library /libr/cons/cons.c of the component radiff2. The manipulation of the argument -T leads to use after free. Local access is required to approach this attack. 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 name 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". A new warning has been added.

References

Community reviews

Loading reviews…