VulnerabilityPublished 14 Nov 2025

CVE-2025-63745: radare2 · CVE-2025-63745 is a medium severity NULL pointer dereference

Affects radare2Source CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 17:16 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:N/UI:R/S:U/C:N/I:N/A:H

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Nov 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 <=6.0.5	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-63745, organizations should first monitor for official patches or updates from the radare2 development team and apply them promptly once available. In the absence of an official patch, users can review and modify the source code of the info() function in bin_ne.c to add proper NULL pointer checks before dereferencing, preventing segmentation faults. Employing input validation and sanitization on binary files before analysis can reduce the risk of triggering the vulnerability. Additionally, running radare2 in isolated or sandboxed environments can contain potential crashes and prevent broader system impact. Security teams should also train users to recognize and avoid processing suspicious or malformed binaries unnecessarily. Incorporating fallback mechanisms or alternative tools for binary analysis can ensure continuity of operations if radare2 becomes unavailable due to exploitation of this vulnerability. Finally, maintaining robust incident response procedures will help quickly address any disruptions caused by denial of service conditions.

Description

CVE-2025-63745 is a medium severity NULL pointer dereference vulnerability in radare2 version 6.0.5 and earlier, specifically in the info() function of bin_ne.c. When processing a crafted malformed binary input, the vulnerability triggers a segmentation fault, causing a denial of service (DoS) by crashing the tool. Exploitation requires local access and user interaction, as the attacker must supply the malformed binary to the tool. There is no impact on confidentiality or integrity, only availability. No known exploits are currently reported in the wild. The vulnerability affects users of radare2, a reverse engineering framework commonly used by security researchers and malware analysts. European organizations relying on radare2 for binary analysis could experience disruption in their workflows if targeted.

Impact

For European organizations, the primary impact of CVE-2025-63745 is the potential disruption of reverse engineering and malware analysis workflows that rely on radare2. Security teams, incident responders, and researchers using this tool may experience denial of service conditions when processing malformed binaries, delaying threat analysis and response times. This could indirectly affect the overall security posture by slowing down detection and mitigation of advanced threats. Organizations involved in software security audits, vulnerability research, and digital forensics may also face operational interruptions. However, since the vulnerability does not compromise confidentiality or integrity, the direct risk of data breach or system compromise is low. The impact is mostly operational and affects availability of a specialized tool rather than critical infrastructure. Nonetheless, in environments where radare2 is integrated into automated pipelines or used extensively, repeated crashes could degrade productivity and increase the risk of missing critical security insights.

CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Nov 2025, 21:55 UTC

WeaknessesCWE-476

Technical details

References

Community reviews

Related threats