UTC
High

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
What it is

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.

What to do

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.

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI>= 4.5.115, < 4.6.614.6.61

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].