PraisonAI: PRAISONAI_CALL_AUTH=disabled environment variable unconditionally disables authentication

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-57132: 0.51% estimated exploitation activity in the next 30 days; percentile 43.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Setting PRAISONAICALLAUTH=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 The application's own error message advertises the bypass: "Set CALLSERVERTOKEN or PRAISONAICALLAUTH=disabled to run without authentication." This causes the setting to appear in Docker/Compose configurations as a convenience option. Proof of Concept Common vulnerable deployment: Impact 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.

Published by the source

18 Jun 2026, 14:27 UTC

Last modified by the source

23 Jul 2026, 15:11 UTC

Source last checked

26 Oct 2026, 13:49 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8ccj-p46r-jwqq

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8ccj-p46r-jwqq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-57132

Advisory: PraisonAI: PRAISONAI_CALL_AUTH=disabled environment variable unconditionally disables authentication
IDs: CVE-2026-57132, GHSA-8ccj-p46r-jwqq
Record: https://patchnext.com/advisories/cve-2026-57132 (revision 2, source checked 26 Oct 2026, 13:49 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai 4.6.61. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected < 4.6.61; fixed in 4.6.61

## Suggested inspection (read-only)
- `python -m pip show praisonai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8ccj-p46r-jwqq (OSV record GHSA-8ccj-p46r-jwqq lists affected ranges: PyPI praisonai >=0 <4.6.61 (fixed))
- Verified: https://github.com/advisories/GHSA-8ccj-p46r-jwqq (GitHub-reviewed advisory GHSA-8ccj-p46r-jwqq lists affected ranges: PyPI praisonai >=0 <4.6.61)

Commands are suggestions: review each one before running it.