<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-17T04:27:52.770717+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-55541</id>
    <title>CVE-2026-55541 — PraisonAI: `--api-key` flag on `praisonai serve` is not properly enforced</title>
    <updated>2026-10-17T04:27:52.772348+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> MervinPraison PraisonAI</p>
<p>PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, praisonai serve agents and praisonai serve unified parse --api-key but _create_agents_app() and _create_unified_app() do not install a credential check. Unauthenticated callers can reach POST /agents and POST /api/v1/agents/{id}/invoke. This issue is fixed in version 4.6.58.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-55541"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pvxx-r596-f5qj</id>
    <title>GHSA-pvxx-r596-f5qj — PraisonAI: `--api-key` flag on `praisonai serve` is not properly enforced</title>
    <updated>2026-10-17T04:27:52.772399+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: PraisonAI</p>
<p>## Summary</p>
<p>`praisonai serve agents` and `praisonai serve unified` both accept `--api-key` for authentication. The flag is parsed but never wired into the FastAPI app — no middleware, no header check, nothing. The server runs wide open regardless of what key you set. Tested on 4.6.50 from PyPI.</p>
<p>## Affected versions</p>
<p>- Confirmed on **4.6.50** (current PyPI, 2026-06-02)
- Likely since **4.6.34** when the serve subsystem shipped
- File: `src/praisonai/praisonai/cli/features/serve.py`</p>
<p>## What happens</p>
<p>The CLI defines `--api-key` in the arg spec (`serve.py:199`) and passes the parsed value into `_create_agents_app(config)`. But that function never reads `config["api_key"]`. The FastAPI app gets created with no auth at all. Same thing in `_create_unified_app`.</p>
<p>The help text says `--api-key &lt;key&gt;   API key for authentication`, so this isn't ambiguous — it's supposed to protect the server. It just doesn't.
```
$ grep -n "api_key" src/praisonai/praisonai/cli/features/serve.py
107:  --api-key &lt;key&gt;   API key for authentication
199:            "api_key": {"default": None},
847:            "api_key": {"default": None},
```</p>
<p>## Endpoints exposed without auth</p>
<p>- `POST /agents` — runs the full agent workflow
- `POST /agents/{name}` — invokes a specific agent
- `POST /api/v1/agents/{id}/invoke` — n8n integration endpoint
- `GET /` — lists all endpoints
- `GET /__praisonai__/discovery` — service discovery</p>
<p>## Not the same as CVE-2026-44338</p>
<p>CVE-2026-44338 was about the legacy `deploy/api.…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pvxx-r596-f5qj"/>
  </entry>
</feed>
