<?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>Mon, 02 Nov 2026 08:38:44 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-57113</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-57113</link>
      <description>&lt;p&gt;PraisonAI is a multi-agent teams system. From version 2.6.0 to before version 4.6.59, PraisonAI&amp;#39;s template loader accepts GitHub template URIs with refs, for example github:owner/repo/template@v1.0.0. The resolver stores the user-controlled template path and ref verbatim, and the cache layer later joins those values into ~/.praison/cache/templates/github/&amp;lt;owner&amp;gt;/&amp;lt;repo&amp;gt;/&amp;lt;template&amp;gt;/&amp;lt;ref&amp;gt; without normalizing each segment or checking that the final path remains inside the template cache root. A crafted ref such as ../../../../../../outside-delete-target therefore escapes the cache directory. The first load can write .cache_meta.json outside the cache. If the normal cache hierarchy for the same owner/repo/template has already been created, the same path reaches shutil.rmtree(cache_path) and removes an attacker-selected outside directory before replacing it with cache metadata. This issue has been patched in version 4.6.59.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PraisonAI is a multi-agent teams system. From version 2.6.0 to before version 4.6.59, PraisonAI&amp;#39;s template loader accepts GitHub template URIs with refs, for example github:owner/repo/template@v1.0.0. The resolver stores the user-controlled template path and ref verbatim, and the cache layer later joins those values into ~/.praison/cache/templates/github/&amp;lt;owner&amp;gt;/&amp;lt;repo&amp;gt;/&amp;lt;template&amp;gt;/&amp;lt;ref&amp;gt; without normalizing each segment or checking that the final path remains inside the template cache root. A crafted ref such as ../../../../../../outside-delete-target therefore escapes the cache directory. The first load can write .cache_meta.json outside the cache. If the normal cache hierarchy for the same owner/repo/template has already been created, the same path reaches shutil.rmtree(cache_path) and removes an attacker-selected outside directory before replacing it with cache metadata. This issue has been patched in version 4.6.59.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-57113</guid>
    </item>
    <item>
      <title>GHSA-f44v-7qgw-9gh9 — PraisonAI GitHub template cache path traversal allows outside-cache file write and directory deletion</title>
      <link>https://db.gcve.eu/vuln/ghsa-f44v-7qgw-9gh9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;PraisonAI&amp;#39;s template loader accepts GitHub template URIs with refs, for example
`github:owner/repo/template@v1.0.0`. The resolver stores the user-controlled
template path and ref verbatim, and the cache layer later joins those values into
`~/.praison/cache/templates/github/&amp;lt;owner&amp;gt;/&amp;lt;repo&amp;gt;/&amp;lt;template&amp;gt;/&amp;lt;ref&amp;gt;` without
normalizing each segment or checking that the final path remains inside the
template cache root.&lt;/p&gt;
&lt;p&gt;A crafted ref such as `../../../../../../outside-delete-target` therefore
escapes the cache directory. The first load can write `.cache_meta.json` outside
the cache. If the normal cache hierarchy for the same owner/repo/template has
already been created, the same path reaches `shutil.rmtree(cache_path)` and
removes an attacker-selected outside directory before replacing it with cache
metadata.&lt;/p&gt;
&lt;p&gt;This is distinct from the old template Zip Slip advisory. No malicious archive
member is needed, and the PoV disables network access entirely. The bug is in
cache-key construction for GitHub template URIs.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;Confirmed vulnerable:&lt;/p&gt;
&lt;p&gt;- `v2.6.0`
- `v3.9.24`
- `v3.9.26`
- `v4.5.126`
- `v4.5.128`
- `v4.6.9`
- `v4.6.10`
- `v4.6.56`
- `v4.6.57`
- current head `2f9677abb2ea68eab864ee8b6a828fd0141612e1`&lt;/p&gt;
&lt;p&gt;Recommended affected range: `&amp;gt;= 2.6.0, &amp;lt;= 4.6.57`.&lt;/p&gt;
&lt;p&gt;No fixed version is known at the time of this report.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can cause a user or service to load an attacker-supplied
PraisonAI GitHub template URI can:&lt;/p&gt;
&lt;p&gt;- create `.cache_meta.json` ou…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;PraisonAI&amp;#39;s template loader accepts GitHub template URIs with refs, for example
`github:owner/repo/template@v1.0.0`. The resolver stores the user-controlled
template path and ref verbatim, and the cache layer later joins those values into
`~/.praison/cache/templates/github/&amp;lt;owner&amp;gt;/&amp;lt;repo&amp;gt;/&amp;lt;template&amp;gt;/&amp;lt;ref&amp;gt;` without
normalizing each segment or checking that the final path remains inside the
template cache root.&lt;/p&gt;
&lt;p&gt;A crafted ref such as `../../../../../../outside-delete-target` therefore
escapes the cache directory. The first load can write `.cache_meta.json` outside
the cache. If the normal cache hierarchy for the same owner/repo/template has
already been created, the same path reaches `shutil.rmtree(cache_path)` and
removes an attacker-selected outside directory before replacing it with cache
metadata.&lt;/p&gt;
&lt;p&gt;This is distinct from the old template Zip Slip advisory. No malicious archive
member is needed, and the PoV disables network access entirely. The bug is in
cache-key construction for GitHub template URIs.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;Confirmed vulnerable:&lt;/p&gt;
&lt;p&gt;- `v2.6.0`
- `v3.9.24`
- `v3.9.26`
- `v4.5.126`
- `v4.5.128`
- `v4.6.9`
- `v4.6.10`
- `v4.6.56`
- `v4.6.57`
- current head `2f9677abb2ea68eab864ee8b6a828fd0141612e1`&lt;/p&gt;
&lt;p&gt;Recommended affected range: `&amp;gt;= 2.6.0, &amp;lt;= 4.6.57`.&lt;/p&gt;
&lt;p&gt;No fixed version is known at the time of this report.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can cause a user or service to load an attacker-supplied
PraisonAI GitHub template URI can:&lt;/p&gt;
&lt;p&gt;- create `.cache_meta.json` ou…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-f44v-7qgw-9gh9</guid>
    </item>
    <item>
      <title>PYSEC-2026-3509 — PraisonAI GitHub template cache path traversal allows outside-cache file write and directory deletion</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-3509</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;PraisonAI&amp;#39;s template loader accepts GitHub template URIs with refs, for example
`github:owner/repo/template@v1.0.0`. The resolver stores the user-controlled
template path and ref verbatim, and the cache layer later joins those values into
`~/.praison/cache/templates/github/&amp;lt;owner&amp;gt;/&amp;lt;repo&amp;gt;/&amp;lt;template&amp;gt;/&amp;lt;ref&amp;gt;` without
normalizing each segment or checking that the final path remains inside the
template cache root.&lt;/p&gt;
&lt;p&gt;A crafted ref such as `../../../../../../outside-delete-target` therefore
escapes the cache directory. The first load can write `.cache_meta.json` outside
the cache. If the normal cache hierarchy for the same owner/repo/template has
already been created, the same path reaches `shutil.rmtree(cache_path)` and
removes an attacker-selected outside directory before replacing it with cache
metadata.&lt;/p&gt;
&lt;p&gt;This is distinct from the old template Zip Slip advisory. No malicious archive
member is needed, and the PoV disables network access entirely. The bug is in
cache-key construction for GitHub template URIs.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;Confirmed vulnerable:&lt;/p&gt;
&lt;p&gt;- `v2.6.0`
- `v3.9.24`
- `v3.9.26`
- `v4.5.126`
- `v4.5.128`
- `v4.6.9`
- `v4.6.10`
- `v4.6.56`
- `v4.6.57`
- current head `2f9677abb2ea68eab864ee8b6a828fd0141612e1`&lt;/p&gt;
&lt;p&gt;Recommended affected range: `&amp;gt;= 2.6.0, &amp;lt;= 4.6.57`.&lt;/p&gt;
&lt;p&gt;No fixed version is known at the time of this report.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can cause a user or service to load an attacker-supplied
PraisonAI GitHub template URI can:&lt;/p&gt;
&lt;p&gt;- create `.cache_meta.json` ou…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: praisonai&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;PraisonAI&amp;#39;s template loader accepts GitHub template URIs with refs, for example
`github:owner/repo/template@v1.0.0`. The resolver stores the user-controlled
template path and ref verbatim, and the cache layer later joins those values into
`~/.praison/cache/templates/github/&amp;lt;owner&amp;gt;/&amp;lt;repo&amp;gt;/&amp;lt;template&amp;gt;/&amp;lt;ref&amp;gt;` without
normalizing each segment or checking that the final path remains inside the
template cache root.&lt;/p&gt;
&lt;p&gt;A crafted ref such as `../../../../../../outside-delete-target` therefore
escapes the cache directory. The first load can write `.cache_meta.json` outside
the cache. If the normal cache hierarchy for the same owner/repo/template has
already been created, the same path reaches `shutil.rmtree(cache_path)` and
removes an attacker-selected outside directory before replacing it with cache
metadata.&lt;/p&gt;
&lt;p&gt;This is distinct from the old template Zip Slip advisory. No malicious archive
member is needed, and the PoV disables network access entirely. The bug is in
cache-key construction for GitHub template URIs.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;Confirmed vulnerable:&lt;/p&gt;
&lt;p&gt;- `v2.6.0`
- `v3.9.24`
- `v3.9.26`
- `v4.5.126`
- `v4.5.128`
- `v4.6.9`
- `v4.6.10`
- `v4.6.56`
- `v4.6.57`
- current head `2f9677abb2ea68eab864ee8b6a828fd0141612e1`&lt;/p&gt;
&lt;p&gt;Recommended affected range: `&amp;gt;= 2.6.0, &amp;lt;= 4.6.57`.&lt;/p&gt;
&lt;p&gt;No fixed version is known at the time of this report.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can cause a user or service to load an attacker-supplied
PraisonAI GitHub template URI can:&lt;/p&gt;
&lt;p&gt;- create `.cache_meta.json` ou…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-3509</guid>
    </item>
  </channel>
</rss>
