Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-57132 – Authentication Bypass – PraisonAI < 4.6.62

Be the first to know when new zero-days emerge:

Summary

CVE-2026-57132 is an improper authentication vulnerability (CWE-287) affecting PraisonAI, a multi-agent orchestration framework. Versions prior to 4.6.62 allow the PRAISONAI_CALL_AUTH=disabled environment variable to unconditionally disable token verification on the agent invocation API, letting unauthenticated attackers invoke registered agents and their connected tools. The issue carries a CVSS v3.1 base score of 8.2 (High).

Technical details

  • Root cause: When the PRAISONAI_CALL_AUTH environment variable is set to disabled, the application’s verify_token function returns immediately without performing any authentication check, skipping validation of the CALL_SERVER_TOKEN.
  • Trigger condition: The bypass is only active when an operator sets PRAISONAI_CALL_AUTH=disabled. However, this opt-out is actively advertised in the application’s own error messages ("Set CALL_SERVER_TOKEN or PRAISONAI_CALL_AUTH=disabled to run without authentication"), making it likely to appear in real-world Docker/Compose deployments where operators disable auth for convenience during setup or testing.
  • Attack vector: Network-based, no privileges or user interaction required. An attacker sends unauthenticated HTTP requests directly to the exposed /api/v1/agents/{id}/invoke endpoint.
  • Impact: Unauthenticated invocation of any registered agent, potentially exposing the agent’s connected tools and private context, and allowing execution of arbitrary agent actions depending on the tools configured. Confidentiality impact is high; integrity impact is low; availability is not affected.

Affected software

  • MervinPraison PraisonAI, all versions prior to 4.6.62

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Upgrade PraisonAI to version 4.6.62 or later, which fixes the issue.
  • If immediate patching is not possible:
    • Remove or avoid setting PRAISONAI_CALL_AUTH=disabled in any production or internet-reachable deployment.
    • Ensure CALL_SERVER_TOKEN is configured and required for all agent invocation requests.
    • Restrict network access to the /api/v1/agents/{id}/invoke endpoint (e.g., via firewall rules, VPN, or reverse proxy authentication) so it is not reachable from untrusted networks.
    • Audit existing deployments and container/Compose configurations for the PRAISONAI_CALL_AUTH=disabled setting and remove it.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge