Skip to main content
CVE-2025-60359VulnerabilityPublished Updated

CVE-2025-60359: radare2 · n/a

Affects radare2Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Oct 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubradareorg/radare2pkg:github/radareorg/radare2Other threatsAffected
  • <=5.9.8
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 CVE-2025-60359, European organizations should: 1) Monitor radare2 project updates and apply patches promptly once available to address the memory leak. 2) If patches are not yet released, consider building radare2 from source with custom memory management fixes or apply community-provided patches addressing CWE-401 issues. 3) Limit local access to systems running radare2 to trusted users only, reducing the risk of exploitation by unauthorized personnel. 4) Implement resource monitoring and automated alerts for unusual memory consumption patterns on systems running radare2 to detect potential exploitation attempts early. 5) Use containerization or sandboxing to isolate radare2 processes, minimizing impact on host system availability. 6) Educate users and administrators about the vulnerability and encourage best practices for secure tool usage. 7) Review and restrict permissions to prevent unprivileged users from invoking vulnerable functions unnecessarily. These steps go beyond generic advice by focusing on access control, monitoring, and interim protective measures pending official patches.

Description

radare2 v5.9.8 and before contains a memory leak in the function r_bin_object_new.

References

Community reviews

Loading reviews…