<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Radare — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/radare/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 23 Apr 2026 21:16:06 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/radare/feed.xml" rel="self" type="application/rss+xml"/><item><title>Radare2 Path Traversal Vulnerability in Project Deletion</title><link>https://feed.craftedsignal.io/briefs/2026-04-radare2-path-traversal/</link><pubDate>Thu, 23 Apr 2026 21:16:06 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-radare2-path-traversal/</guid><description>Radare2 versions prior to 6.1.4 are vulnerable to a path traversal in project deletion, allowing local attackers to recursively delete arbitrary directories by escaping the 'dir.projects' root, leading to integrity and availability loss.</description><content:encoded><![CDATA[<p>Radare2, a reverse engineering framework, is susceptible to a path traversal vulnerability (CVE-2026-6940) affecting versions prior to 6.1.4. This flaw allows a local attacker to delete arbitrary directories outside of the intended project storage location. By crafting project marker files with absolute paths that escape the configured <code>dir.projects</code> root directory, an attacker can trick the radare2 process into recursively deleting directories they should not have access to. This vulnerability poses a significant risk to system integrity and availability, as attackers can potentially delete critical system files or data. This vulnerability was published on 2026-04-23 and could be exploited immediately.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains local access to a system with radare2 installed.</li>
<li>Attacker identifies the location where radare2 stores project files (configured by <code>dir.projects</code>).</li>
<li>Attacker crafts a malicious radare2 project file containing an absolute path pointing outside the designated project directory. This path includes traversal sequences (e.g., <code>../</code>) to escape the <code>dir.projects</code> root.</li>
<li>The attacker places the malicious project marker file in a location where radare2 will discover it (e.g. a default projects directory).</li>
<li>Attacker uses radare2&rsquo;s project deletion functionality, specifying the malicious project for deletion.</li>
<li>Radare2, without proper validation of the project file path, recursively deletes the directory specified in the crafted path.</li>
<li>This deletion occurs with the permissions of the radare2 process, potentially allowing the attacker to delete files and directories they would normally not have access to.</li>
<li>The attacker achieves arbitrary directory deletion, leading to loss of system integrity and availability.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows a local attacker to recursively delete arbitrary directories on the affected system. This can lead to significant data loss, system instability, and denial of service. The CVSS v3.1 base score for this vulnerability is 7.1, indicating a high level of severity. While no specific victim numbers or sector targeting have been disclosed, the potential impact on any system running a vulnerable version of radare2 is substantial.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade radare2 to version 6.1.4 or later to patch CVE-2026-6940.</li>
<li>Implement the process creation rule below to detect suspicious radare2 executions that could indicate exploitation attempts.</li>
<li>Consider limiting local user access to systems running radare2 to reduce the attack surface.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>path-traversal</category><category>radare2</category><category>local-privilege-escalation</category></item><item><title>radare2 PDB Parser Command Injection Vulnerability (CVE-2026-40517)</title><link>https://feed.craftedsignal.io/briefs/2024-01-radare2-command-injection/</link><pubDate>Wed, 24 Jan 2024 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-radare2-command-injection/</guid><description>A command injection vulnerability exists in radare2 versions prior to 6.1.4, where a crafted PDB file with newline characters in symbol names can inject arbitrary radare2 commands, leading to arbitrary OS command execution.</description><content:encoded><![CDATA[<p>A command injection vulnerability, identified as CVE-2026-40517, affects radare2 versions prior to 6.1.4. This flaw resides within the PDB parser&rsquo;s <code>print_gvars()</code> function. An attacker can exploit this vulnerability by creating a malicious PDB file containing newline characters within symbol names. These newline characters enable the injection of arbitrary radare2 commands, which are then executed due to unsanitized symbol name interpolation. This interpolation occurs during the execution of the <code>idp</code> command against the malicious PDB file. Successful exploitation allows the attacker to achieve arbitrary OS command execution through radare2&rsquo;s shell execution operator, posing a significant risk to systems where radare2 is used for binary analysis.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker crafts a malicious PDB file. This file contains newline characters embedded within symbol names.</li>
<li>The crafted PDB file is delivered to the target system, potentially through social engineering or as part of a larger attack chain.</li>
<li>A user, unaware of the malicious nature of the PDB file, attempts to analyze it using radare2.</li>
<li>The user executes the <code>idp</code> command within radare2 to parse and load debug symbols from the PDB file.</li>
<li>During the parsing process, the <code>print_gvars()</code> function is called within the PDB parser.</li>
<li>The function attempts to rename flags based on the symbol names read from the PDB file.</li>
<li>Due to the lack of proper sanitization, the newline characters in the symbol names are interpreted as command separators.</li>
<li>The injected radare2 commands are executed by the shell execution operator, leading to arbitrary OS command execution. The attacker achieves arbitrary command execution on the system.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an attacker to execute arbitrary commands on the system where radare2 is running. The impact ranges from system compromise and data theft to denial of service, depending on the privileges of the user running radare2 and the commands injected by the attacker. The CVSS v3.1 base score is rated as 7.8 (High).</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade radare2 to version 6.1.4 or later to patch CVE-2026-40517.</li>
<li>Implement strict input validation and sanitization for PDB files processed by radare2 to prevent command injection.</li>
<li>Deploy the Sigma rule <code>Detect Suspicious Radare2 Process Execution</code> to identify potential exploitation attempts.</li>
<li>Monitor radare2 process execution for unusual command line arguments (see <code>Detect Suspicious Radare2 Process Execution</code>).</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>command-injection</category><category>radare2</category><category>CVE-2026-40517</category></item></channel></rss>