CVE-2026-57127
Received Received - Intake

Authentication Bypass in PraisonAI Recipe Serve

Publication date: 2026-09-14

Last updated on: 2026-09-14

Assigner: GitHub, Inc.

Description
PraisonAI is a multi-agent teams system. Prior to 4.6.58, recipe serve installs APIKeyAuthMiddleware or JWTAuthMiddleware when an operator selects api-key or JWT authentication, but each middleware forwards requests when PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET and the corresponding recipe value are absent. Unauthenticated clients can then reach recipe execution, input, and output surfaces and may trigger connected tools despite the operator explicitly enabling authentication. This issue is fixed in 4.6.58.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-14
Last Modified
2026-09-14
Generated
2026-09-15
AI Q&A
2026-09-14
EPSS Evaluated
N/A
NVD
CVE-2026-57127
EUVD
EUVD-2026-77615

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
praisonai praisonai to 4.6.58 (inc)
mervinpraison praisonai 4.6.58
mervinpraison praisonai to 4.6.48 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
CWE-1188 The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects PraisonAI versions 4.6.48 and earlier. It involves the recipe serve authentication middleware disabling itself when no secret (API key or JWT secret) is configured, even if the operator set an auth type in the recipe YAML. The middleware allows requests to bypass authentication entirely if no secret is provided, either via YAML or environment variables. This happens because the middleware fails open instead of failing closed, allowing unauthorized access to recipe execution endpoints.

Detection Guidance

Check PraisonAI version with pip show praisonai or grep version in installed files. Verify if recipe serve is running with api-key or JWT auth enabled but no secret configured. Inspect middleware logs for authentication bypass events or unexpected request forwarding.

Impact Analysis

Unauthenticated attackers can reach recipe execution, input, and output surfaces. They may trigger connected tools, read in-flight recipe inputs and outputs, and potentially gain remote code execution if the recipe uses tools like browser automation or file-system access. This could lead to unauthorized actions or data breaches.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. It may result in data breaches, unauthorized processing, or disclosure of personal or health data, leading to legal and regulatory penalties.

Mitigation Strategies

Upgrade PraisonAI to version 4.6.58 or later. Ensure API key or JWT secret is properly configured in recipe YAML or environment variables. Disable affected recipes until patched. Monitor for unauthorized access attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57127. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart