Skip to main content
CVE-2025-60360VulnerabilityPublished Updated

CVE-2025-60360: radare2 · n/a

Affects radare2Source CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

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

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

1. Restrict local access to systems running radare2 to trusted users only, minimizing the risk of exploitation by unauthorized personnel. 2. Monitor memory usage of radare2 processes, especially those invoking subprocess initialization, to detect abnormal resource consumption early. 3. Employ containerization or sandboxing techniques to isolate radare2 executions, limiting the impact of memory leaks on host systems. 4. Regularly update radare2 to the latest versions once patches addressing CVE-2025-60360 become available. 5. Implement system-level resource limits (e.g., cgroups on Linux) to prevent any single process from exhausting system memory. 6. Educate security and development teams about the vulnerability and encourage cautious use of radare2 subprocess features. 7. Consider alternative tools or workflows temporarily if radare2 usage is critical and patches are delayed. 8. Maintain robust logging and alerting on system performance anomalies related to radare2 activity.

Description

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

References

Community reviews

Loading reviews…