<?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-10T07:04:54.427738+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-57128</id>
    <title>CVE-2026-57128 — PraisonAI: Unauthenticated Event Injection via SSE `/publish` Endpoint</title>
    <updated>2026-10-10T07:04:54.429607+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 praisonaiagents 1.6.58, the SSE server in src/praisonai-agents/praisonaiagents/server/server.py does not consult ServerConfig.auth_token before handling /publish, /events, or /info requests. A network client that can reach the server can broadcast arbitrary events to connected clients and obtain server configuration and client-count information. This issue is fixed in praisonaiagents 1.6.58.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-57128"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-35w5-pcw4-jx94</id>
    <title>GHSA-35w5-pcw4-jx94 — PraisonAI: Unauthenticated Event Injection via SSE `/publish` Endpoint</title>
    <updated>2026-10-10T07:04:54.429661+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: praisonaiagents</p>
<p>## Summary</p>
<p>The SSE (Server-Sent Events) server in `src/praisonai-agents/praisonaiagents/server/server.py` exposes a `/publish` endpoint that broadcasts arbitrary messages to all connected clients without any authentication. The `ServerConfig` dataclass (line 24) defines an `auth_token` field, but this token is never validated in the `/publish` or `/events` request handlers. Any attacker with access to the SSE server port can inject arbitrary events into the SSE stream visible to all connected clients, or use `/info` to leak server configuration including connected client count.</p>
<p>## Details</p>
<p>**Vulnerable code (lines 164–180):**
```python
async def publish(request):
    try:
        data = await request.json()
        event_type = data.get("type", "message")
        event_data = data.get("data", {})</p>
<p>self.broadcast(event_type, event_data)</p>
<p>return JSONResponse({
            "success": True,
            "clients": len(self._clients),
        })
```</p>
<p>The `auth_token` field in `ServerConfig` (line 31):
```python
@dataclass
class ServerConfig:
    ...
    auth_token: Optional[str] = None
```</p>
<p>This `auth_token` is **never referenced** in any request handler. The `/publish` endpoint processes any POST request regardless of authentication headers. The `/info` endpoint (line 182) also has no auth and returns server configuration including `self.config.to_dict()`.</p>
<p>**Routes registration (lines 190–194):**
```python
routes = [
    Route("/health", health, methods=["GET"]…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-35w5-pcw4-jx94"/>
  </entry>
</feed>
