CVE-2025-60360

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

Published: 2025-10-17 Last update: 2025-10-23 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-60360 is rated Low Risk (22.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-60360

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-10-18 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-60360

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-60360

OS Trackers for CVE-2025-60360

vendor priority summary link
alpine — CVE-2025-60360: 1 source package rows (radare2); 38 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 38. https://security.alpinelinux.org/vuln/CVE-2025-60360
debian not yet assigned CVE-2025-60360 not yet assigned priority: Debian including 1 source packages (radare2), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-60360
ubuntu medium CVE-2025-60360 medium priority: Ubuntu including 1 source packages (radare2), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): needs-triage 5, DNE 1, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-60360

Affected software / configurations for CVE-2025-60360

Vendor Product Version Raw CPE
radare radare2 <= 5.9.8 cpe:2.3:a:radare:radare2:*:*:*:*:*:*:*:*

References for CVE-2025-60360

URL Tags
https://github.com/radareorg/radare2/pull/24245 Issue Tracking Third Party Advisory
cvelogic Threat Intelligence