CVE-2025-5641
Last modified
CVE-2025-5641 is a low-severity vulnerability rated 2.5/10 on the CVSS scale. A vulnerability was found in Radare2 5.9.9. It has been rated as problematic. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
A vulnerability was found in Radare2 5.9.9. It has been rated as problematic. This issue affects the function r_cons_is_breaked in the library /libr/cons/cons.c of the component radiff2. The manipulation of the argument -T leads to memory corruption. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The real existence of this vulnerability is still doubted at the moment. The identifier of the patch is 5705d99cc1f23f36f9a84aab26d1724010b97798. It is recommended to apply a patch to fix this issue. The documentation explains that the parameter -T is experimental and "crashy". Further analysis has shown "the race is not a real problem unless you use asan". An additional warning regarding threading support has been added.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Radare | Radare2 | 5.9.9 |
References
- https://github.com/radareorg/radare2/issues/24230Exploit, Issue Tracking, Vendor Advisory
- https://github.com/radareorg/radare2/issues/24230#issuecomment-2919612676Issue Tracking, Vendor Advisory
- https://vuldb.com/?ctiid.311129Permissions Required, VDB Entry
- https://vuldb.com/?id.311129Third Party Advisory, VDB Entry
- https://vuldb.com/?submit.586909Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-5641?
How severe is CVE-2025-5641?
How do I fix CVE-2025-5641?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-56400Cross-Site Request Forgery (CSRF) vulnerability in the OAuth…8.8
- CVE-2025-56401ZIRA Group WBRM 7.0 is vulnerable to SQL Injection in refere…7.6
- CVE-2025-56404An issue was discovered in MariaDB MCP 0.1.0 allowing attack…7.5
- CVE-2025-56405An issue was discovered in litmusautomation litmus-mcp-serve…7.5
- CVE-2025-56406An issue was discovered in mcp-neo4j 0.3.0 allowing attacker…7.5
- CVE-2025-56407A vulnerability has been found in HuangDou UTCMS V9 and clas…8.8
- CVE-2025-56413OS Command injection vulnerability in function OperateSSH in…8.8
- CVE-2025-5642A vulnerability classified as problematic has been found in …2.5
- CVE-2025-56421SQL Injection vulnerability in LimeSurvey before v.6.15.4+25…7.5
- CVE-2025-56422A deserialization vulnerability in LimeSurvey before v6.15.0…9.8
- CVE-2025-56423An issue in Austrian Academy of Sciences (AW) Austrian Archa…5.3
- CVE-2025-56424An issue in Insiders Technologies GmbH e-invoice pro before …7.5
Are you affected by CVE-2025-5641?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
