<?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>Sat, 03 Oct 2026 13:28:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-290882</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-290882</link>
      <description>EUVD-2026-290882</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-290882</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40149</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40149</link>
      <description>&lt;p&gt;PraisonAI is a multi-agent teams system. Prior to 4.5.128, the gateway&amp;#39;s /api/approval/allow-list endpoint permits unauthenticated modification of the tool approval allowlist when no auth_token is configured (the default). By adding dangerous tool names (e.g., shell_exec, file_write) to the allowlist, an attacker can cause the ExecApprovalManager to auto-approve all future agent invocations of those tools, bypassing the human-in-the-loop safety mechanism that the approval system is specifically designed to enforce. This vulnerability is fixed in 4.5.128.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PraisonAI is a multi-agent teams system. Prior to 4.5.128, the gateway&amp;#39;s /api/approval/allow-list endpoint permits unauthenticated modification of the tool approval allowlist when no auth_token is configured (the default). By adding dangerous tool names (e.g., shell_exec, file_write) to the allowlist, an attacker can cause the ExecApprovalManager to auto-approve all future agent invocations of those tools, bypassing the human-in-the-loop safety mechanism that the approval system is specifically designed to enforce. This vulnerability is fixed in 4.5.128.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40149</guid>
    </item>
    <item>
      <title>GHSA-4wr3-f4p3-5wjh — PraisonAI: Unauthenticated Allow-List Manipulation Bypasses Agent Tool Approval Safety Controls</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4wr3-f4p3-5wjh</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;The gateway&amp;#39;s `/api/approval/allow-list` endpoint permits unauthenticated modification of the tool approval allowlist when no `auth_token` is configured (the default). By adding dangerous tool names (e.g., `shell_exec`, `file_write`) to the allowlist, an attacker can cause the `ExecApprovalManager` to auto-approve all future agent invocations of those tools, bypassing the human-in-the-loop safety mechanism that the approval system is specifically designed to enforce.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The vulnerability arises from the interaction of three components:&lt;/p&gt;
&lt;p&gt;**1. Authentication bypass in default config**&lt;/p&gt;
&lt;p&gt;`_check_auth()` in `server.py:243-246` returns `None` (no error) when `self.config.auth_token` is falsy:&lt;/p&gt;
&lt;p&gt;```python
# server.py:243-246
def _check_auth(request) -&amp;gt; Optional[JSONResponse]:
    if not self.config.auth_token:
        return None  # No auth configured → allow everything
```&lt;/p&gt;
&lt;p&gt;`GatewayConfig` defaults `auth_token` to `None` (`config.py:61`):&lt;/p&gt;
&lt;p&gt;```python
# config.py:61
auth_token: Optional[str] = None
```&lt;/p&gt;
&lt;p&gt;**2. Unrestricted allowlist modification**&lt;/p&gt;
&lt;p&gt;The `approval_allowlist` handler at `server.py:381-420` calls `_check_auth()` and proceeds when it returns `None`:&lt;/p&gt;
&lt;p&gt;```python
# server.py:388-410
auth_err = _check_auth(request)
if auth_err:
    return auth_err
# ...
if request.method == &amp;#34;POST&amp;#34;:
    _approval_mgr.allowlist.add(tool_name)  # No validation on tool_name
    return JSONResponse({&amp;#34;added&amp;#34;: tool_name})
```&lt;/p&gt;
&lt;p&gt;There is no validation that `tool_name` corresponds t…&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;The gateway&amp;#39;s `/api/approval/allow-list` endpoint permits unauthenticated modification of the tool approval allowlist when no `auth_token` is configured (the default). By adding dangerous tool names (e.g., `shell_exec`, `file_write`) to the allowlist, an attacker can cause the `ExecApprovalManager` to auto-approve all future agent invocations of those tools, bypassing the human-in-the-loop safety mechanism that the approval system is specifically designed to enforce.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The vulnerability arises from the interaction of three components:&lt;/p&gt;
&lt;p&gt;**1. Authentication bypass in default config**&lt;/p&gt;
&lt;p&gt;`_check_auth()` in `server.py:243-246` returns `None` (no error) when `self.config.auth_token` is falsy:&lt;/p&gt;
&lt;p&gt;```python
# server.py:243-246
def _check_auth(request) -&amp;gt; Optional[JSONResponse]:
    if not self.config.auth_token:
        return None  # No auth configured → allow everything
```&lt;/p&gt;
&lt;p&gt;`GatewayConfig` defaults `auth_token` to `None` (`config.py:61`):&lt;/p&gt;
&lt;p&gt;```python
# config.py:61
auth_token: Optional[str] = None
```&lt;/p&gt;
&lt;p&gt;**2. Unrestricted allowlist modification**&lt;/p&gt;
&lt;p&gt;The `approval_allowlist` handler at `server.py:381-420` calls `_check_auth()` and proceeds when it returns `None`:&lt;/p&gt;
&lt;p&gt;```python
# server.py:388-410
auth_err = _check_auth(request)
if auth_err:
    return auth_err
# ...
if request.method == &amp;#34;POST&amp;#34;:
    _approval_mgr.allowlist.add(tool_name)  # No validation on tool_name
    return JSONResponse({&amp;#34;added&amp;#34;: tool_name})
```&lt;/p&gt;
&lt;p&gt;There is no validation that `tool_name` corresponds t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4wr3-f4p3-5wjh</guid>
    </item>
    <item>
      <title>PYSEC-2026-2901 — PraisonAI: Unauthenticated Allow-List Manipulation Bypasses Agent Tool Approval Safety Controls</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2901</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;The gateway&amp;#39;s `/api/approval/allow-list` endpoint permits unauthenticated modification of the tool approval allowlist when no `auth_token` is configured (the default). By adding dangerous tool names (e.g., `shell_exec`, `file_write`) to the allowlist, an attacker can cause the `ExecApprovalManager` to auto-approve all future agent invocations of those tools, bypassing the human-in-the-loop safety mechanism that the approval system is specifically designed to enforce.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The vulnerability arises from the interaction of three components:&lt;/p&gt;
&lt;p&gt;**1. Authentication bypass in default config**&lt;/p&gt;
&lt;p&gt;`_check_auth()` in `server.py:243-246` returns `None` (no error) when `self.config.auth_token` is falsy:&lt;/p&gt;
&lt;p&gt;```python
# server.py:243-246
def _check_auth(request) -&amp;gt; Optional[JSONResponse]:
    if not self.config.auth_token:
        return None  # No auth configured → allow everything
```&lt;/p&gt;
&lt;p&gt;`GatewayConfig` defaults `auth_token` to `None` (`config.py:61`):&lt;/p&gt;
&lt;p&gt;```python
# config.py:61
auth_token: Optional[str] = None
```&lt;/p&gt;
&lt;p&gt;**2. Unrestricted allowlist modification**&lt;/p&gt;
&lt;p&gt;The `approval_allowlist` handler at `server.py:381-420` calls `_check_auth()` and proceeds when it returns `None`:&lt;/p&gt;
&lt;p&gt;```python
# server.py:388-410
auth_err = _check_auth(request)
if auth_err:
    return auth_err
# ...
if request.method == &amp;#34;POST&amp;#34;:
    _approval_mgr.allowlist.add(tool_name)  # No validation on tool_name
    return JSONResponse({&amp;#34;added&amp;#34;: tool_name})
```&lt;/p&gt;
&lt;p&gt;There is no validation that `tool_name` corresponds t…&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;The gateway&amp;#39;s `/api/approval/allow-list` endpoint permits unauthenticated modification of the tool approval allowlist when no `auth_token` is configured (the default). By adding dangerous tool names (e.g., `shell_exec`, `file_write`) to the allowlist, an attacker can cause the `ExecApprovalManager` to auto-approve all future agent invocations of those tools, bypassing the human-in-the-loop safety mechanism that the approval system is specifically designed to enforce.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The vulnerability arises from the interaction of three components:&lt;/p&gt;
&lt;p&gt;**1. Authentication bypass in default config**&lt;/p&gt;
&lt;p&gt;`_check_auth()` in `server.py:243-246` returns `None` (no error) when `self.config.auth_token` is falsy:&lt;/p&gt;
&lt;p&gt;```python
# server.py:243-246
def _check_auth(request) -&amp;gt; Optional[JSONResponse]:
    if not self.config.auth_token:
        return None  # No auth configured → allow everything
```&lt;/p&gt;
&lt;p&gt;`GatewayConfig` defaults `auth_token` to `None` (`config.py:61`):&lt;/p&gt;
&lt;p&gt;```python
# config.py:61
auth_token: Optional[str] = None
```&lt;/p&gt;
&lt;p&gt;**2. Unrestricted allowlist modification**&lt;/p&gt;
&lt;p&gt;The `approval_allowlist` handler at `server.py:381-420` calls `_check_auth()` and proceeds when it returns `None`:&lt;/p&gt;
&lt;p&gt;```python
# server.py:388-410
auth_err = _check_auth(request)
if auth_err:
    return auth_err
# ...
if request.method == &amp;#34;POST&amp;#34;:
    _approval_mgr.allowlist.add(tool_name)  # No validation on tool_name
    return JSONResponse({&amp;#34;added&amp;#34;: tool_name})
```&lt;/p&gt;
&lt;p&gt;There is no validation that `tool_name` corresponds t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2901</guid>
    </item>
  </channel>
</rss>
