<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 17:58:55 +0000</lastBuildDate>
    <item>
      <title>PYSEC-2026-3522 — PraisonAI: Compute-bridged file tools allow shell command injection</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-3522</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# Compute-bridged file tools allow shell command injection&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`LocalManagedAgent` / `SandboxedAgent` compute bridging wraps
`read_file`, `list_files`, and `write_file` when a compute provider is
attached. The bridge converts those file operations into shell command strings
using raw path arguments, then sends those strings to shell-backed compute
providers.&lt;/p&gt;
&lt;p&gt;An attacker who can influence a file-tool path argument can break out of the
quoted path and execute arbitrary shell commands in the compute environment.
With `compute=&amp;#34;local&amp;#34;`, commands execute through the local subprocess compute
provider on the host. With Docker, commands execute in the container.&lt;/p&gt;
&lt;p&gt;## Affected Product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Package: `praisonai`
- Component: `src/praisonai/praisonai/integrations/managed_local.py`
- Confirmed affected:
  - `v4.6.10`
  - `v4.6.56`
  - `v4.6.57`
  - current `main` at `2f9677abb2ea68eab864ee8b6a828fd0141612e1`
- Confirmed not affected:
  - `v4.6.9`
  - `v4.6.1`
  - `v4.5.149`
- Suggested affected range: `&amp;gt;= 4.6.10, &amp;lt;= 4.6.57`&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;Current `managed_local.py` defines the bridged tool set:&lt;/p&gt;
&lt;p&gt;```python
compute_bridged_tools = {&amp;#34;execute_command&amp;#34;, &amp;#34;read_file&amp;#34;, &amp;#34;write_file&amp;#34;, &amp;#34;list_files&amp;#34;}
```&lt;/p&gt;
&lt;p&gt;For file tools, `_bridge_file_tool()` constructs shell command strings:&lt;/p&gt;
&lt;p&gt;```python
command = f&amp;#39;cat &amp;#34;{filepath}&amp;#34;&amp;#39;
command = f&amp;#39;ls -la &amp;#34;{directory}&amp;#34;&amp;#39;
command = f&amp;#39;cat &amp;gt; &amp;#34;{filepath}&amp;#34; &amp;lt;&amp;lt; &amp;#34;EOF&amp;#34;\n{content}\nEOF&amp;#39;
```&lt;/p&gt;
&lt;p&gt;The local compute provider executes the st…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# Compute-bridged file tools allow shell command injection&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`LocalManagedAgent` / `SandboxedAgent` compute bridging wraps
`read_file`, `list_files`, and `write_file` when a compute provider is
attached. The bridge converts those file operations into shell command strings
using raw path arguments, then sends those strings to shell-backed compute
providers.&lt;/p&gt;
&lt;p&gt;An attacker who can influence a file-tool path argument can break out of the
quoted path and execute arbitrary shell commands in the compute environment.
With `compute=&amp;#34;local&amp;#34;`, commands execute through the local subprocess compute
provider on the host. With Docker, commands execute in the container.&lt;/p&gt;
&lt;p&gt;## Affected Product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Package: `praisonai`
- Component: `src/praisonai/praisonai/integrations/managed_local.py`
- Confirmed affected:
  - `v4.6.10`
  - `v4.6.56`
  - `v4.6.57`
  - current `main` at `2f9677abb2ea68eab864ee8b6a828fd0141612e1`
- Confirmed not affected:
  - `v4.6.9`
  - `v4.6.1`
  - `v4.5.149`
- Suggested affected range: `&amp;gt;= 4.6.10, &amp;lt;= 4.6.57`&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;Current `managed_local.py` defines the bridged tool set:&lt;/p&gt;
&lt;p&gt;```python
compute_bridged_tools = {&amp;#34;execute_command&amp;#34;, &amp;#34;read_file&amp;#34;, &amp;#34;write_file&amp;#34;, &amp;#34;list_files&amp;#34;}
```&lt;/p&gt;
&lt;p&gt;For file tools, `_bridge_file_tool()` constructs shell command strings:&lt;/p&gt;
&lt;p&gt;```python
command = f&amp;#39;cat &amp;#34;{filepath}&amp;#34;&amp;#39;
command = f&amp;#39;ls -la &amp;#34;{directory}&amp;#34;&amp;#39;
command = f&amp;#39;cat &amp;gt; &amp;#34;{filepath}&amp;#34; &amp;lt;&amp;lt; &amp;#34;EOF&amp;#34;\n{content}\nEOF&amp;#39;
```&lt;/p&gt;
&lt;p&gt;The local compute provider executes the st…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-3522</guid>
    </item>
  </channel>
</rss>
