CVE-2026-57127: praisonai: recipe serve auth middleware silently disables itself when no secret is set

Published Sep 14, 2026
·
Updated

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 PRAISONAIAPIKEY or PRAISONAIJWTSECRET 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.

Affected Software

1 affected component
PraisonAI PraisonAI<4.6.58

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PraisonAI (praisonai: recipe serve) to a version that resolves this vulnerability.

    Fixed in 4.6.58
  2. Operational

    Ensure PRAISONAI_API_KEY is set when using api-key authentication and ensure PRAISONAI_JWT_SECRET is set when using JWT authentication, so the corresponding auth middleware (APIKeyAuthMiddleware or JWTAuthMiddleware) does not silently disable itself due to missing secrets.

Event History

Sep 14, 2026
CVE Published
via MITRE·03:01 PM
Data Sourced
via MITRE·03:01 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to unauthenticated access?

PraisonAI deployments prior to 4.6.58 are exposed when recipe serve is configured to use API-key or JWT authentication but both the relevant environment secret and corresponding recipe value are absent. In that state, the selected authentication middleware forwards requests instead of rejecting them.

2

What does an attacker need to exploit this issue?

An attacker only needs network access to the affected recipe serve endpoint. No credentials or user interaction are required when the authentication middleware has silently disabled itself.

3

What could an unauthenticated client access or trigger?

Unauthenticated clients can reach recipe execution, input, and output surfaces. They may also trigger connected tools.

4

How can operators remediate or reduce exposure?

Upgrade PraisonAI to version 4.6.58. If upgrading is not immediately possible, ensure the applicable PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET environment variable and its corresponding recipe value are configured, and restrict network access to the recipe serve endpoint.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203