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

Back
New CVE Detected

CVE-2026-57127 – Authentication Bypass / RCE Risk – PraisonAI ≤ 4.6.48

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-57127 is a critical missing-authentication vulnerability in PraisonAI’s "recipe serve" feature. When an operator configures API key or JWT authentication in the recipe YAML but does not provide the corresponding secret, the authentication middleware silently disables itself and allows unauthenticated access to recipe execution endpoints. The flaw carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: In praisonai/recipe/serve.py, the APIKeyAuthMiddleware and JWTAuthMiddleware classes check whether an expected API key or JWT secret is configured before enforcing authentication. If PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET (or the equivalent recipe configuration) is absent, the middleware’s dispatch logic takes a fail-open path (e.g., if not expected_key: return await call_next(request)) and forwards the request instead of rejecting it.
  • Trigger conditions: An operator enables auth: api-key or auth: jwt for a served recipe but does not set the corresponding secret via configuration or environment variable — a plausible and easy-to-make misconfiguration since authentication appears to be "on."
  • Attack vector: Network-based, no authentication or user interaction required, low attack complexity — any remote party able to reach the exposed recipe serve HTTP endpoint can send requests directly.
  • Impact: Attackers can trigger arbitrary recipe executions with attacker-controlled inputs, read the inputs and outputs of in-flight recipes, and potentially achieve remote code execution if the recipe pipeline is wired to system tools, shells, or other connected integrations.

Affected software

  • Product: PraisonAI (praisonai package on PyPI), maintained by MervinPraison
  • Affected versions: All versions up to and including 4.6.48 (confirmed tested on 4.6.48; no earlier "introduced" version is specified, so all prior releases should be treated as affected)
  • Fixed version: 4.6.59 and later

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade PraisonAI to version 4.6.59 or later, where the authentication middleware correctly rejects requests when no secret is configured.
  • If immediate patching is not possible:
    • Explicitly set PRAISONAI_API_KEY or PRAISONAI_JWT_SECRET (as appropriate) for any deployment using recipe serve with auth: api-key or auth: jwt enabled, and verify the secret is actually loaded at runtime.
    • Restrict network exposure of recipe serve endpoints to trusted internal networks or behind a properly authenticated reverse proxy/VPN until patched.
    • Audit recipe configurations to confirm authentication is actually being enforced (e.g., test with no credentials to verify requests are rejected) rather than assuming configuration alone provides protection.
    • Review logs for recipe execution requests from unexpected or unauthenticated sources.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge