VulnerabilityPublished 17 Oct 2025Updated 20 Oct 2025

CVE-2025-60361: radare2 · Memory Leak

Affects radare2Source CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

3.3Low

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:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component 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 remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
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 impacted component 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 impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Oct 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 26 Oct 2026.

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 or the CVSS exploit maturity 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.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

Monitor radare2 project communications and repositories for official patches addressing CVE-2025-60361 and apply updates promptly once available.
Restrict local access to systems running radare2 to trusted users only, minimizing the risk of exploitation by unauthorized personnel.
Implement resource monitoring tools to track memory usage of radare2 processes, enabling early detection of abnormal consumption patterns indicative of the memory leak.
Consider running radare2 in isolated or containerized environments to limit the impact of potential memory exhaustion on host systems.
For automated analysis pipelines, schedule periodic restarts of radare2 processes to clear accumulated memory usage until a patch is applied.
Educate security analysts and developers about this vulnerability to ensure awareness and encourage reporting of any unusual application behavior.
Evaluate alternative reverse engineering tools temporarily if the memory leak significantly impacts operational stability.

Description

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

Impact

For European organizations, the primary impact of this vulnerability is potential degradation of availability in systems running vulnerable versions of radare2. Memory leaks can cause increased memory consumption, leading to application crashes or system instability, especially in environments where radare2 is used extensively or in automated pipelines. While the vulnerability does not expose sensitive data or allow unauthorized code execution, it can disrupt security analysis workflows or delay incident response activities. Organizations relying on radare2 for malware analysis, reverse engineering, or forensic investigations may experience reduced operational efficiency. The impact is mitigated by the requirement for local access and the low severity rating. However, in high-security environments or critical infrastructure sectors where radare2 is part of the toolchain, even minor availability issues can have cascading effects.

CWE-401Missing Release of Memory after Effective Lifetime (opens in a new tab)
Variant weaknessLikelihood of exploit: Medium
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Implementation · Libraries or Frameworks
Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Architecture and Design · Build and Compilation
Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/radareorg/radare2/pull/24312 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2025, 18:17 UTC

WeaknessesCWE-401

Technical details

References

Community reviews

Related threats