<?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://db.gcve.eu</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>Sat, 24 Oct 2026 23:11:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-56833 — PraisonAI Dynamic Context history and terminal tools read files outside configured storage via path traversal</title>
      <link>https://db.gcve.eu/vuln/cve-2026-56833</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MervinPraison PraisonAI&lt;/p&gt;
&lt;p&gt;PraisonAI is a multi-agent teams system. From version 3.8.1 to before version 4.6.59, PraisonAI&amp;#39;s Dynamic Context module provides filesystem-backed history and terminal-log storage. The module also exports agent-callable tool factories. Those tools accept run_id and agent_id arguments from the tool caller. The underlying stores join those values into filesystem paths without rejecting absolute paths or .. traversal. Because run_id can be an absolute path and agent_id can contain traversal, a lower-trust prompt/user that can call these tools can read .jsonl and .log files outside the configured Dynamic Context base directory. This issue has been patched in version 4.6.59.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; MervinPraison PraisonAI&lt;/p&gt;
&lt;p&gt;PraisonAI is a multi-agent teams system. From version 3.8.1 to before version 4.6.59, PraisonAI&amp;#39;s Dynamic Context module provides filesystem-backed history and terminal-log storage. The module also exports agent-callable tool factories. Those tools accept run_id and agent_id arguments from the tool caller. The underlying stores join those values into filesystem paths without rejecting absolute paths or .. traversal. Because run_id can be an absolute path and agent_id can contain traversal, a lower-trust prompt/user that can call these tools can read .jsonl and .log files outside the configured Dynamic Context base directory. This issue has been patched in version 4.6.59.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-56833</guid>
    </item>
    <item>
      <title>PYSEC-2026-3499 — PraisonAI Dynamic Context history and terminal tools read files outside configured storage via path traversal</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-3499</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# PraisonAI Dynamic Context history and terminal tools read files outside configured storage via path traversal&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;PraisonAI&amp;#39;s Dynamic Context module provides filesystem-backed history and
terminal-log storage. The SDK reference describes the module as providing:&lt;/p&gt;
&lt;p&gt;- artifact storage for tool outputs, history, and terminal logs;
- history persistence with search; and
- terminal session logging.&lt;/p&gt;
&lt;p&gt;The module also exports agent-callable tool factories:&lt;/p&gt;
&lt;p&gt;- `create_history_tools()` returns `history_search`, `history_tail`, and
  `history_get`.
- `create_terminal_tools()` returns `terminal_tail`, `terminal_grep`, and
  `terminal_commands`.&lt;/p&gt;
&lt;p&gt;Those tools accept `run_id` and `agent_id` arguments from the tool caller. The
underlying stores join those values into filesystem paths without rejecting
absolute paths or `..` traversal:&lt;/p&gt;
&lt;p&gt;```python
history_dir = self.base_dir / run_id / &amp;#34;history&amp;#34;
return history_dir / f&amp;#34;{agent_id}.jsonl&amp;#34;
```&lt;/p&gt;
&lt;p&gt;```python
terminal_dir = self.base_dir / run_id / &amp;#34;terminal&amp;#34;
return terminal_dir / f&amp;#34;{agent_id}.log&amp;#34;
```&lt;/p&gt;
&lt;p&gt;Because `run_id` can be an absolute path and `agent_id` can contain traversal,
a lower-trust prompt/user that can call these tools can read `.jsonl` and
`.log` files outside the configured Dynamic Context base directory.&lt;/p&gt;
&lt;p&gt;## Affected Product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Ecosystem: `pip`
- Package: `praisonai`
- Component: Dynamic Context history and terminal tools
- Current source paths:
  - `src/praisonai/praisonai/context/hist…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;# PraisonAI Dynamic Context history and terminal tools read files outside configured storage via path traversal&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;PraisonAI&amp;#39;s Dynamic Context module provides filesystem-backed history and
terminal-log storage. The SDK reference describes the module as providing:&lt;/p&gt;
&lt;p&gt;- artifact storage for tool outputs, history, and terminal logs;
- history persistence with search; and
- terminal session logging.&lt;/p&gt;
&lt;p&gt;The module also exports agent-callable tool factories:&lt;/p&gt;
&lt;p&gt;- `create_history_tools()` returns `history_search`, `history_tail`, and
  `history_get`.
- `create_terminal_tools()` returns `terminal_tail`, `terminal_grep`, and
  `terminal_commands`.&lt;/p&gt;
&lt;p&gt;Those tools accept `run_id` and `agent_id` arguments from the tool caller. The
underlying stores join those values into filesystem paths without rejecting
absolute paths or `..` traversal:&lt;/p&gt;
&lt;p&gt;```python
history_dir = self.base_dir / run_id / &amp;#34;history&amp;#34;
return history_dir / f&amp;#34;{agent_id}.jsonl&amp;#34;
```&lt;/p&gt;
&lt;p&gt;```python
terminal_dir = self.base_dir / run_id / &amp;#34;terminal&amp;#34;
return terminal_dir / f&amp;#34;{agent_id}.log&amp;#34;
```&lt;/p&gt;
&lt;p&gt;Because `run_id` can be an absolute path and `agent_id` can contain traversal,
a lower-trust prompt/user that can call these tools can read `.jsonl` and
`.log` files outside the configured Dynamic Context base directory.&lt;/p&gt;
&lt;p&gt;## Affected Product&lt;/p&gt;
&lt;p&gt;- Repository: `MervinPraison/PraisonAI`
- Ecosystem: `pip`
- Package: `praisonai`
- Component: Dynamic Context history and terminal tools
- Current source paths:
  - `src/praisonai/praisonai/context/hist…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-3499</guid>
    </item>
  </channel>
</rss>
