<?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://cve.radiocsirt.org</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, 06 Oct 2026 06:54:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-44340 — PraisonAI: Symlink-extraction bypass of `_safe_extractall` writes outside `dest_dir`</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-44340</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. Prior to version 4.6.37, the _safe_extractall helper that all recipe pull, recipe publish, and recipe unpack flows route through validates each archive member&amp;#39;s name for absolute paths, .. segments, and resolved-path escape — but does not validate member.linkname, does not reject symlink/hardlink members, and calls tar.extractall(dest_dir) without filter=&amp;#34;data&amp;#34;. A bundle that contains a symlink with a name inside dest_dir but a linkname pointing outside it, followed by a regular file whose path traverses through the just-created symlink, escapes dest_dir and lets the attacker write arbitrary content to an attacker-chosen location on the victim&amp;#39;s filesystem. This issue has been patched in version 4.6.37.&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. Prior to version 4.6.37, the _safe_extractall helper that all recipe pull, recipe publish, and recipe unpack flows route through validates each archive member&amp;#39;s name for absolute paths, .. segments, and resolved-path escape — but does not validate member.linkname, does not reject symlink/hardlink members, and calls tar.extractall(dest_dir) without filter=&amp;#34;data&amp;#34;. A bundle that contains a symlink with a name inside dest_dir but a linkname pointing outside it, followed by a regular file whose path traverses through the just-created symlink, escapes dest_dir and lets the attacker write arbitrary content to an attacker-chosen location on the victim&amp;#39;s filesystem. This issue has been patched in version 4.6.37.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-44340</guid>
    </item>
    <item>
      <title>GHSA-9q28-ghcr-c4x3 — PraisonAI's symlink-extraction bypass of `_safe_extractall` writes outside `dest_dir`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9q28-ghcr-c4x3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: PraisonAI&lt;/p&gt;
&lt;p&gt;### Summary
The `_safe_extractall` helper that all `recipe pull`, `recipe publish`, and `recipe unpack` flows route through validates each archive member&amp;#39;s `name` for absolute paths, `..` segments, and resolved-path escape — but does **not** validate `member.linkname`, does not reject symlink/hardlink members, and calls `tar.extractall(dest_dir)` without `filter=&amp;#34;data&amp;#34;`. A bundle that contains a symlink with a name
inside `dest_dir` but a `linkname` pointing outside it, followed by a regular file whose path traverses *through* the just-created symlink, escapes `dest_dir` and lets the attacker write arbitrary content to an attacker-chosen location on the victim&amp;#39;s filesystem.&lt;/p&gt;
&lt;p&gt;## Affected paths&lt;/p&gt;
&lt;p&gt;Every code path that calls `_safe_extractall` is exposed:&lt;/p&gt;
&lt;p&gt;| Caller | File:line |
|---|---|
| `praisonai recipe unpack` | `src/praisonai/praisonai/cli/features/recipe.py:1175` (introduced as the fix for GHSA-99g3-w8gr-x37c) |
| `LocalRegistry.unpack` (recipe pull) | `src/praisonai/praisonai/recipe/registry.py:413` |
| Registry archive validation (publish) | `src/praisonai/praisonai/recipe/registry.py:808` |&lt;/p&gt;
&lt;p&gt;## Root cause&lt;/p&gt;
&lt;p&gt;`recipe/registry.py:131-178`:&lt;/p&gt;
&lt;p&gt;```python
def _safe_extractall(tar: tarfile.TarFile, dest_dir: Path) -&amp;gt; None:
    ...
    for member in tar.getmembers():
        ...
        member_path = Path(member.name)
        if member_path.is_absolute(): raise RegistryError(...)
        if &amp;#39;..&amp;#39; in member_path.parts: raise RegistryError(...)
        resolved = (dest_resolved / me…&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
The `_safe_extractall` helper that all `recipe pull`, `recipe publish`, and `recipe unpack` flows route through validates each archive member&amp;#39;s `name` for absolute paths, `..` segments, and resolved-path escape — but does **not** validate `member.linkname`, does not reject symlink/hardlink members, and calls `tar.extractall(dest_dir)` without `filter=&amp;#34;data&amp;#34;`. A bundle that contains a symlink with a name
inside `dest_dir` but a `linkname` pointing outside it, followed by a regular file whose path traverses *through* the just-created symlink, escapes `dest_dir` and lets the attacker write arbitrary content to an attacker-chosen location on the victim&amp;#39;s filesystem.&lt;/p&gt;
&lt;p&gt;## Affected paths&lt;/p&gt;
&lt;p&gt;Every code path that calls `_safe_extractall` is exposed:&lt;/p&gt;
&lt;p&gt;| Caller | File:line |
|---|---|
| `praisonai recipe unpack` | `src/praisonai/praisonai/cli/features/recipe.py:1175` (introduced as the fix for GHSA-99g3-w8gr-x37c) |
| `LocalRegistry.unpack` (recipe pull) | `src/praisonai/praisonai/recipe/registry.py:413` |
| Registry archive validation (publish) | `src/praisonai/praisonai/recipe/registry.py:808` |&lt;/p&gt;
&lt;p&gt;## Root cause&lt;/p&gt;
&lt;p&gt;`recipe/registry.py:131-178`:&lt;/p&gt;
&lt;p&gt;```python
def _safe_extractall(tar: tarfile.TarFile, dest_dir: Path) -&amp;gt; None:
    ...
    for member in tar.getmembers():
        ...
        member_path = Path(member.name)
        if member_path.is_absolute(): raise RegistryError(...)
        if &amp;#39;..&amp;#39; in member_path.parts: raise RegistryError(...)
        resolved = (dest_resolved / me…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9q28-ghcr-c4x3</guid>
    </item>
  </channel>
</rss>
