GHSA-8CCJ-P46R-JWQQ

Setting PRAISONAI_CALL_AUTH=disabled completely disables all authentication on the /api/v1/agents/{id}/invoke endpoint. This bypass is advertised in the application's own error messages, making it likely to appear in production Docker and Compose configurations.

Details

# src/praisonai/praisonai/api/agent_invoke.py:32
_CALL_AUTH_DISABLED = os.getenv('PRAISONAI_CALL_AUTH', '').lower() == 'disabled'

async def verify_token(...) -> None:
    if _CALL_AUTH_DISABLED:
        return  # all authentication skipped unconditionally

The application's own error message advertises the bypass:

"Set CALL_SERVER_TOKEN or PRAISONAI_CALL_AUTH=disabled to run without authentication."

This causes the setting to appear in Docker/Compose configurations as a convenience option.

Proof of Concept

import os
os.environ["PRAISONAI_CALL_AUTH"] = "disabled"
# verify_token() now returns immediately for any request
# POST /api/v1/agents/any-agent/invoke → 200 OK (no token needed)

Common vulnerable deployment:

# docker-compose.yml
environment:
  - PRAISONAI_CALL_AUTH=disabled  # auth completely disabled

Full unauthenticated access to the agent invocation API. Any agent registered on the server can be triggered without credentials, potentially executing arbitrary actions depending on the agent's configured tools.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

GHSA-8CCJ-P46R-JWQQ has a CVSS score of 8.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.6.61); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-8CCJ-P46R-JWQQ? GHSA-8CCJ-P46R-JWQQ is a high-severity improper authentication vulnerability in praisonai (pip), affecting versions < 4.6.61. It is fixed in 4.6.61. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is GHSA-8CCJ-P46R-JWQQ? GHSA-8CCJ-P46R-JWQQ has a CVSS score of 8.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of praisonai are affected by GHSA-8CCJ-P46R-JWQQ? praisonai (pip) versions < 4.6.61 is affected.
4. Is there a fix for GHSA-8CCJ-P46R-JWQQ? Yes. GHSA-8CCJ-P46R-JWQQ is fixed in 4.6.61. Upgrade to this version or later.
5. Is GHSA-8CCJ-P46R-JWQQ exploitable, and should I be worried? Whether GHSA-8CCJ-P46R-JWQQ is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-8CCJ-P46R-JWQQ is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-8CCJ-P46R-JWQQ? Upgrade praisonai to 4.6.61 or later.