<?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>Wed, 07 Oct 2026 15:50:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-55538 — PraisonAI: [Auth Bypass] `praisonai serve agents --api-key` is silently ignored — agent-invocation routes (`POST /agent…</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-55538</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 praisonai 4.6.51, praisonai serve agents parses config[&amp;#34;api_key&amp;#34;] but _create_agents_app() does not authenticate POST /agents or POST /agents/{agent_name}. Missing or incorrect bearer and X-API-Key values still reach agent execution. This issue is fixed in version 4.6.58.&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 praisonai 4.6.51, praisonai serve agents parses config[&amp;#34;api_key&amp;#34;] but _create_agents_app() does not authenticate POST /agents or POST /agents/{agent_name}. Missing or incorrect bearer and X-API-Key values still reach agent execution. This issue is fixed in version 4.6.58.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-55538</guid>
    </item>
    <item>
      <title>GHSA-r7v3-x45f-g7hp — PraisonAI: [Auth Bypass] `praisonai serve agents --api-key` is silently ignored — agent-invocation routes (`POST /agent…</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-r7v3-x45f-g7hp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: PraisonAI&lt;/p&gt;
&lt;p&gt;### Summary
`praisonai serve agents` exposes HTTP routes that invoke registered agents. The CLI advertises `--api-key` with help text &amp;#34;API key for authentication&amp;#34;, parses it, and forwards it into `ServeHandler`. But `_create_agents_app()` **never reads `config[&amp;#34;api_key&amp;#34;]` again** and installs no auth dependency or middleware on its direct routes. The configured key is a no-op flag.
 
As a result, an unauthenticated network caller can invoke exposed agents (`POST /agents` and `POST /agents/{agent_name}`) even when the operator passed `--api-key`. Requests with no credentials, a wrong `Authorization: Bearer`, a wrong `X-API-Key`, or an empty bearer all reach `agent.start()`.
 
The failure is made sharper by the fact that a **working auth dependency already exists in the same module** — `praisonai.api.agent_invoke.verify_token` guards every `/api/v1/...` route with `Depends(verify_token)` and is mounted into the very same app. The direct n8n-compat routes simply do not use it.&lt;/p&gt;
&lt;p&gt;## Technical Detail
 
### Source-to-sink trace
 
**1. CLI advertises and forwards `--api-key`:**
 
```python
# cli/commands/serve.py
@app.command(&amp;#34;agents&amp;#34;)
def serve_agents(..., api_key: Optional[str] = typer.Option(None, &amp;#34;--api-key&amp;#34;, help=&amp;#34;API key for authentication&amp;#34;)):
    ...
    if api_key:
        args.extend([&amp;#34;--api-key&amp;#34;, api_key])
    exit_code = handle_serve_command(args)
```
 
**2. `cmd_agents()` parses `api_key` into the spec — and that is the last time it is touched:**
 
```python
# cli/featur…&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
`praisonai serve agents` exposes HTTP routes that invoke registered agents. The CLI advertises `--api-key` with help text &amp;#34;API key for authentication&amp;#34;, parses it, and forwards it into `ServeHandler`. But `_create_agents_app()` **never reads `config[&amp;#34;api_key&amp;#34;]` again** and installs no auth dependency or middleware on its direct routes. The configured key is a no-op flag.
 
As a result, an unauthenticated network caller can invoke exposed agents (`POST /agents` and `POST /agents/{agent_name}`) even when the operator passed `--api-key`. Requests with no credentials, a wrong `Authorization: Bearer`, a wrong `X-API-Key`, or an empty bearer all reach `agent.start()`.
 
The failure is made sharper by the fact that a **working auth dependency already exists in the same module** — `praisonai.api.agent_invoke.verify_token` guards every `/api/v1/...` route with `Depends(verify_token)` and is mounted into the very same app. The direct n8n-compat routes simply do not use it.&lt;/p&gt;
&lt;p&gt;## Technical Detail
 
### Source-to-sink trace
 
**1. CLI advertises and forwards `--api-key`:**
 
```python
# cli/commands/serve.py
@app.command(&amp;#34;agents&amp;#34;)
def serve_agents(..., api_key: Optional[str] = typer.Option(None, &amp;#34;--api-key&amp;#34;, help=&amp;#34;API key for authentication&amp;#34;)):
    ...
    if api_key:
        args.extend([&amp;#34;--api-key&amp;#34;, api_key])
    exit_code = handle_serve_command(args)
```
 
**2. `cmd_agents()` parses `api_key` into the spec — and that is the last time it is touched:**
 
```python
# cli/featur…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-r7v3-x45f-g7hp</guid>
    </item>
  </channel>
</rss>
