CVE-2026-55533

PraisonAI: Authentication fail-open in Recipe server allows unauthenticated access when API key or JWT auth is configured without a secret

Published Aug 25, 2026 CVSS 3.1 · 8.2 High EPSS < 1% KEV · Not listed
Description
PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, create_auth_middleware() allows requests when auth=api-key lacks PRAISONAI_API_KEY or JWT authentication lacks PRAISONAI_JWT_SECRET. An externally bound Recipe server can therefore accept unauthenticated POST /v1/recipes/run requests despite authentication being enabled. This issue is fixed in version 4.6.58.

Analysis

AI-generated

Technical impact

The vulnerability is a fail‑open in the authentication middleware of PraisonAI. When the application is set to use API‑key or JWT authentication but the required secret variables PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET are missing, the middleware accepts all requests. An attacker who can reach the externally bound Recipe server can therefore trigger the /v1/recipes/run endpoint without providing any credentials, resulting in a bypass of access controls for that resource.

Affected Systems

The flaw applies to PraisonAI releases before version 4.6.58, including 4.6.57 and older, produced by MervinPraison. The issue is limited to the Recipe server component that processes POST requests for recipe execution.

Risk and Exploitability

The CVSS base score of 8.2 indicates high severity, and the vulnerability is exploitable over the network from any external host that can reach the Recipe server’s API. Because the exploit requires no additional credentials and can be performed by simply sending a crafted HTTP request, the risk is that an attacker could execute arbitrary recipes or other privileged operations. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, but the high CVSS and the documented remote availability make it a significant threat, especially for deployments that expose the Recipe endpoint to the internet.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade PraisonAI to version 4.6.58 or later.
  • If an upgrade cannot be performed immediately, configure the environment variables PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET with strong, non‑empty values before starting the service, thereby enforcing authentication.
  • Consider restricting network access to the Recipe server or disabling the /v1/recipes/run endpoint until the vulnerability can be remediated.

Generated by OpenCVE AI on August 25, 2026 at 16:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-gfq8-hmph-9gjv PraisonAI: Authentication fail-open in Recipe server allows unauthenticated access when API key or JWT auth is configured without a secret
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mervinpraison
Mervinpraison praisonai
Vendors & Products Mervinpraison
Mervinpraison praisonai
Type Values Removed Values Added
Description PraisonAI is a multi-agent teams system. Prior to praisonai 4.6.58, create_auth_middleware() allows requests when auth=api-key lacks PRAISONAI_API_KEY or JWT authentication lacks PRAISONAI_JWT_SECRET. An externally bound Recipe server can therefore accept unauthenticated POST /v1/recipes/run requests despite authentication being enabled. This issue is fixed in version 4.6.58.
Title PraisonAI: Authentication fail-open in Recipe server allows unauthenticated access when API key or JWT auth is configured without a secret
Weaknesses CWE-287
CWE-306
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N'}

Weaknesses
  • CWE-287

    Improper Authentication

  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 25, 2026, 4:12 PM
Reserved
Jun 16, 2026, 11:01 PM
Status
Deferred
Published
Aug 25, 2026, 4:16 PM
Modified
Sep 9, 2026, 9:07 PM