CVE-2026-57132: PraisonAI: PRAISONAI_CALL_AUTH=disabled environment variable unconditionally disables authentication

Published Sep 14, 2026
·
Updated

PraisonAI is a multi-agent teams system. Prior to 4.6.62, setting PRAISONAICALLAUTH to disabled makes verifytoken accept requests to /api/v1/agents/{id}/invoke without CALLSERVERTOKEN authentication. Deployments that use the application's advertised opt-out can expose registered agents and their connected tools or private context to unauthenticated invocation. The vulnerability is fixed in 4.6.62.

Affected Software

1 affected component
PraisonAI PraisonAI<4.6.62

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PraisonAI to a version that resolves this vulnerability.

    Fixed in 4.6.62
  2. Configuration

    Do not set PRAISONAI_CALL_AUTH=disabled; it unconditionally disables authentication and, in versions prior to 4.6.62, allows unauthenticated requests to /api/v1/agents/{id}/invoke that bypass CALL_SERVER_TOKEN authentication via verify_token.

    PraisonAI PRAISONAI_CALL_AUTH = disabled

Event History

Sep 14, 2026
CVE Published
via MITRE·03:09 PM
Data Sourced
via MITRE·03:09 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to unauthenticated agent invocation?

PraisonAI deployments running a version before 4.6.62 are exposed if PRAISONAI_CALL_AUTH is set to disabled. This advertised authentication opt-out causes requests to the agent invocation endpoint to be accepted without a CALL_SERVER_TOKEN.

2

What does an attacker need to exploit this issue?

An attacker does not need authentication, privileges, or user interaction when the affected environment variable setting is in use. They need network access to the /api/v1/agents/{id}/invoke endpoint and an agent ID to invoke a registered agent.

3

What is the impact of successful exploitation?

Unauthenticated callers can invoke registered agents. Depending on the deployed agents, this can expose connected tools or private context.

4

How can I determine whether my deployment is affected?

Check whether the PraisonAI version is earlier than 4.6.62 and whether PRAISONAI_CALL_AUTH is set to disabled. Deployments meeting both conditions should be treated as affected.

5

What should be done if an immediate upgrade is not possible?

Do not set PRAISONAI_CALL_AUTH to disabled, and ensure CALL_SERVER_TOKEN authentication remains required for the invocation endpoint. Upgrade to version 4.6.62 when possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203