CVE-2026-57146: PraisonAI A2U incomplete authentication fix leaves current serve command unauthenticated by default
PraisonAI is a multi-agent teams system. From version 4.5.115 to before version 4.6.61, the published A2U advisory GHSA-f292-66h9-fpmf says unauthenticated A2U event streaming was fixed in praisonai 4.5.115. Current head still exposes the same A2U subscription and event routes without authentication when the operator starts the documented CLI entrypoint. The current CLI wrapper does not expose --api-key, does not install the common API-key middleware, and does not generate a token for A2U. It calls createa2uroutes(app) directly. That helper only enforces auth if A2UAUTHTOKEN is already present; if the variable is missing, authenticaterequest() returns None and treats auth as disabled. This issue has been patched in version 4.6.61.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
praisonaito a version that resolves this vulnerability.Fixed in 4.6.61 - Configuration
Set A2U_AUTH_TOKEN before starting the CLI entrypoint so A2U request authentication is enabled.
PraisonAI A2U A2U_AUTH_TOKEN = non-empty secret token
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments running praisonai from version 4.5.115 through versions before 4.6.61 are affected when started through the documented CLI entrypoint and A2U_AUTH_TOKEN is not set. In that configuration, the A2U subscription and event routes are exposed without authentication.
What does an attacker need to access the affected routes?
An attacker needs network access to the A2U service endpoints. No credentials or prior privileges are required when authentication is disabled by the absent A2U_AUTH_TOKEN variable.
Is the documented CLI configuration secure by default?
No. The current CLI wrapper does not expose an --api-key option, install the common API-key middleware, or generate an A2U token; authentication is only enabled if A2U_AUTH_TOKEN has already been supplied.
What can be done before upgrading?
Set A2U_AUTH_TOKEN so that the A2U route helper enforces authentication. Upgrade to praisonai version 4.6.61 when possible.
How can I check whether my instance is currently exposed?
Check whether the installed praisonai version is at least 4.5.115 and earlier than 4.6.61, whether it is launched through the documented CLI entrypoint, and whether A2U_AUTH_TOKEN is unset. If all apply, its A2U subscription and event routes are unauthenticated.