PraisonAI A2U incomplete authentication fix leaves current serve command unauthenticated by default
CVE-2026-57146 · GHSA-jxcw-qp4h-6jfq · published 2026-06-18 · updated 2026-07-20
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 0.49%
- Fixed in
- 4.6.61
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
An attacker who can reach a current A2U server started without A2UAUTHTOKEN can subscribe to agent event streams without credentials. The prior public advisory already classifies the exposed data as agent responses, tool calls, thinking/progress events, and stream metadata. If operators rely on the published fixed version or the secure-by-default serve documentation, they may expose A2U on a network interface believing the unauthenticated stream issue is fixed.
Upgrade praisonai to 4.6.61 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Recommended: 1. Make praisonai serve a2u secure by default in the same way as the documented API servers: generate a bearer token when none is configured, print it to stderr, and enforce it on all non-public A2U endpoints. 2. Add --api-key / --auth-token support to the dedicated A2U command and pass the configured token into createa2uroutes() or shared middleware. 3. Fail closed for external binds such as --host 0.0.0.0 unless authentication is enabled. 4. Require auth on /a2u/health or remove subscription and stream counts from unauthenticated health responses. 5.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | >= 4.5.115, < 4.6.61 | 4.6.61 |
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- CriticalPraisonAI: AICoder Arbitrary File Write and Command Execution via LLM Tool Callspraisonai
- CriticalPraisonAI: Code Injection via f-string Interpolation in Deploy API Server Generationpraisonai
- CriticalPraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92praisonai
- CriticalPraisonAI: Arbitrary File Read/Write via `multiedit` Tool Without Path Validationpraisonai
- CriticalPraisonAI: Unauthenticated RCE via Jobs API + Approval Bypasspraisonaiagents, praisonai
- CriticalPraisonAI: AgentOS remains unauthenticated after incomplete fix version and allows remote agent invocationpraisonai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.