<?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>HKUDS — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/hkuds/</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, 30 Apr 2026 22:17:40 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/hkuds/feed.xml" rel="self" type="application/rss+xml"/><item><title>HKUDS OpenHarness Remote Code Execution via /bridge Slash Command (CVE-2026-7551)</title><link>https://feed.craftedsignal.io/briefs/2026-05-openharness-rce/</link><pubDate>Thu, 30 Apr 2026 22:17:40 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-openharness-rce/</guid><description>HKUDS OpenHarness contains a remote code execution vulnerability (CVE-2026-7551) in the /bridge slash command, allowing remote attackers to execute arbitrary operating system commands by injecting malicious commands via the /bridge spawn command, leading to unauthorized shell access and data exposure.</description><content:encoded><![CDATA[<p>HKUDS OpenHarness is vulnerable to a remote code execution flaw (CVE-2026-7551) affecting the /bridge slash command. This vulnerability permits remote attackers, who are authorized by the OpenHarness configuration, to execute arbitrary operating system commands on the host system. The attack leverages the /bridge spawn command, which, when supplied with attacker-controlled command text, is processed by the bridge session manager and executed through a shared shell subprocess. This execution context grants attackers the ability to spawn shell sessions with the privileges of the OpenHarness process user, potentially exposing local files, credentials, workspace state, and repository contents. Successful exploitation results in a complete compromise of the OpenHarness instance.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies an accessible OpenHarness instance with the vulnerable /bridge slash command enabled.</li>
<li>The attacker authenticates or gains access to a communication channel (e.g., chat application) accepted by OpenHarness.</li>
<li>The attacker crafts a malicious /bridge spawn command containing OS commands to be executed.</li>
<li>The attacker sends the crafted /bridge spawn command to the OpenHarness instance via the configured communication channel.</li>
<li>OpenHarness processes the /bridge command and forwards the attacker-controlled command text to the bridge session manager.</li>
<li>The bridge session manager executes the injected OS commands through a shared shell subprocess.</li>
<li>The attacker gains a shell session with the privileges of the OpenHarness process user.</li>
<li>The attacker accesses local files, credentials, workspace state, and repository contents, potentially exfiltrating sensitive data or establishing persistence.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-7551 allows attackers to execute arbitrary operating system commands on the OpenHarness server. This grants them the ability to spawn shell sessions as the OpenHarness process user, which can lead to the exposure of sensitive information such as local files, credentials, workspace state, and repository contents. The impact of this vulnerability is significant, potentially allowing for complete system compromise and data exfiltration, but the exact number of victims is currently unknown.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply available patches or updates provided by HKUDS to address CVE-2026-7551 on all OpenHarness instances.</li>
<li>Implement input validation and sanitization on the /bridge slash command to prevent the injection of malicious OS commands.</li>
<li>Monitor process creation events for suspicious shell executions originating from the OpenHarness process using the provided Sigma rule.</li>
<li>Restrict network access to the OpenHarness server to only authorized users and systems.</li>
<li>Review OpenHarness configurations to ensure that only trusted communication channels are accepted.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>rce</category><category>vulnerability</category><category>injection</category></item></channel></rss>