CVE-2026-57147: PraisonAI JWT authentication bypass with hardcoded secret

CVE-2026-57147 · Severity: critical · CVSS 9.8 · Published 2026-09-15

PraisonAI is a multi-agent team system platform with API endpoints protected by JWT authentication. When the JWT secret is not explicitly configured and the environment is not explicitly set to production, the platform falls back to a publicly known default secret key, allowing unauthenticated attackers to forge valid authentication tokens and gain unauthorized access to protected API endpoints.

Technologies: praisonai-platform (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-57147 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-57147 being exploited in the wild.
How severe is CVE-2026-57147?
Critical severity, with a CVSS score of 9.8, published 15 September 2026.
Which products and versions are affected?
praisonai-platform (PyPI) ECOSYSTEM:introduced=0,fixed=0.1.6.
Is there a fix for CVE-2026-57147?
Yes. praisonai-platform (PyPI): upgrade to 0.1.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57147 attacked?
It is attacked over the network.
Am I affected by CVE-2026-57147?
Check whether you run praisonai-platform (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • praisonai-platform (PyPI): upgrade to 0.1.6 or later
    pip install "praisonai-platform>=0.1.6"

Technical details

The vulnerability is an authentication bypass in praisonai_platform/services/auth_service.py stemming from unsafe JWT secret defaults. When the PLATFORM_JWT_SECRET environment variable is unset, the service assigns the hardcoded, publicly known value "dev-secret-change-me" as the JWT signing key. Additionally, the PLATFORM_ENV environment variable defaults to "dev" when unset, preventing the production guard that would reject insecure configurations from executing. A remote unauthenticated attacker can mint HS256 JWT tokens with arbitrary claims (sub, email) and authenticate to protected API routes without legitimate credentials. The AuthService._verify_token() and get_current_user() functions accept these forged tokens. This vulnerability is fixed in version 0.1.6 by no longer defaulting PLATFORM_ENV to dev and auto-generating an ephemeral random secret with a warning when PLATFORM_JWT_SECRET is absent in non-dev environments.

Affected products

  • MervinPraison PraisonAI before 0.1.6

Identifiers

  • CVE-2026-57147
  • GHSA-cwj8-7gp2-ggcw
  • PYSEC-2026-3524

Timeline

  • 2026-09-15: disclosed
  • 2026-06-03: patched: Fixed in commit e0fb8e7 and released in version 0.1.6

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.