Summary
CVE-2026-57148 is a critical authentication bypass vulnerability in praisonai-platform, the platform/backend component of the PraisonAI multi-agent framework. The service falls back to a hardcoded, publicly known JWT signing secret (dev-secret-change-me) whenever the PLATFORM_JWT_SECRET environment variable is not explicitly set, and the guard meant to block this in production never fires because it only checks PLATFORM_ENV, which itself defaults to "dev". The flaw allows any unauthenticated network attacker to forge valid session tokens and impersonate arbitrary users, including workspace owners, and carries a CVSS v3.1 score of 9.8 (Critical).
Technical details
- Root cause:
auth_service.pyin praisonai-platform signs and validates JWTs using a default constant (dev-secret-change-me) whenPLATFORM_JWT_SECRETis not configured. A production-safety guard exists but only raises an error whenPLATFORM_ENV != "dev"; sincePLATFORM_ENVdefaults to"dev"and is not set by standard deployment instructions, the guard silently never activates. - Trigger conditions: The vulnerability is present in any default deployment of praisonai-platform where operators have not manually set
PLATFORM_JWT_SECRETandPLATFORM_ENVto production-safe values — which, per the advisory, describes the vast majority of real-world installs. - Attack vector: Network-based, no authentication or user interaction required. An attacker only needs to know (or look up) the publicly disclosed default secret string to mint a valid HS256-signed JWT with an arbitrary
sub/emailclaim. - Impact: Full authentication bypass and account takeover, including impersonation of workspace owners/admins. This can lead to unauthorized data access, resource deletion, and eviction of legitimate workspace members — compromising confidentiality, integrity, and availability of the platform.
- History: This CVE represents an incomplete/regressed fix for an earlier advisory (GHSA-3qg8-5g3r-79v5 / CVE-2026-47410) that had claimed version 0.1.4 as remediated; version 0.1.4 was later found to still contain the same flawed guard logic.
Affected software
- praisonai-platform (PyPI package): versions 0.1.0 through 0.1.4 (inclusive)
- Deployments running from the unpatched
mainbranch prior to the fix commit are also affected
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-platformto version 0.1.6 or later, which removes reliance on the insecure default secret/guard logic. - If immediate patching is not possible:
- Explicitly set a strong, unique
PLATFORM_JWT_SECRETenvironment variable in every deployment — never allow the application to fall back to its built-in default. - Explicitly set
PLATFORM_ENVto a non-devvalue (e.g.,production) in all production and internet-facing deployments so any remaining safety checks are triggered. - Rotate all existing JWT secrets and force re-authentication of all users after upgrading, since any tokens forged prior to remediation should be considered compromised.
- Restrict network exposure of the praisonai-platform authentication endpoints until the upgrade and secret rotation are completed.
- Explicitly set a strong, unique

