CVE-2026-61427: PraisonAI before 4.6.78 Authentication Bypass via HTTP-stream

Published Jul 15, 2026
·
Updated

PraisonAI before 4.6.78 exposes the MCP HTTP-stream transport without authentication by default: the CLI --api-key option defaults to None, and the server only enforces Authorization/Bearer checks when an API key is configured. When an operator runs 'praisonai mcp serve --transport http-stream' without an API key, an unauthenticated client (no Authorization header, and no Origin header, which is also permitted) can initialize a session, enumerate the available tools (tools/list), and invoke tools (tools/call). Additionally, the dispatcher forwards tool-call arguments to handlers without validating them against the advertised inputSchema. The server binds to 127.0.0.1 by default, so remote exploitation requires the operator to bind to a network-accessible address (e.g., --host 0.0.0.0).

Affected Software

1 affected component
PraisonAI praisonai<4.6.78

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PraisonAI to a version that resolves this vulnerability.

    Fixed in 4.6.78
  2. Configuration

    Run 'praisonai mcp serve --transport http-stream' with the CLI --api-key configured to a value, so the server enforces Authorization/Bearer checks.

    PraisonAI MCP HTTP-stream server (praisonai mcp serve) --api-key (CLI option default None) = set a non-None API key
  3. Configuration

    Bind the MCP server to 127.0.0.1 (default) and avoid binding to a network-accessible address like --host 0.0.0.0 to prevent remote unauthenticated exploitation.

    PraisonAI MCP HTTP-stream server (praisonai mcp serve) --host = 127.0.0.1
  4. Compensating control

    Ensure access to the MCP serve endpoint is restricted externally (e.g., only reachable from trusted hosts), since remote exploitation requires the operator to bind to a network-accessible address (e.g., --host 0.0.0.0).

Event History

Jul 15, 2026
CVE Published
via MITRE·11:25 AM
Data Sourced
via MITRE·11:25 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:18 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-61427?

The severity of CVE-2026-61427 is medium, rated at 6.9 according to the CVSS metrics.

2

How do I fix CVE-2026-61427?

To fix CVE-2026-61427, upgrade to PraisonAI version 4.6.78 or later, which enforces authentication by default.

3

What type of vulnerability is CVE-2026-61427?

CVE-2026-61427 is an authentication bypass vulnerability that occurs due to improper default configurations in PraisonAI.

4

What systems are affected by CVE-2026-61427?

CVE-2026-61427 affects all versions of PraisonAI prior to 4.6.78 when using the HTTP-stream transport.

5

What risk does CVE-2026-61427 pose?

CVE-2026-61427 poses a risk as it allows unauthorized access to the MCP HTTP-stream transport without proper authentication.

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