CVE-2026-47410 affects PraisonAI Platform versions before 0.1.4. The vulnerability arises from the use of a hard-coded cryptographic key for JWT signing: the default secret is the literal "dev-secret-change-me" when the environment variable PLATFORM_JWT_SECRET is not set. The platform includes a safety check that disables this default only if PLATFORM_ENV is not set to "dev"; since the default environment is "dev", this check is bypassed in typical deployments. An attacker can read the hard-coded secret from the public source, then mint JWT tokens with arbitrary subject and email claims, allowing authentication as any user, including workspace owners and administrators. This leads to full compromise of authentication and authorization controls. The issue is patched in version 0.1.4.

Successful exploitation allows an unauthenticated attacker to generate valid JWT tokens with arbitrary user claims, enabling impersonation of any user, including privileged roles such as workspace owners and administrators. This results in complete compromise of authentication and authorization mechanisms, leading to full system access and control. The vulnerability has a CVSS 3.1 score of 9.8 (critical), reflecting its high impact on confidentiality, integrity, and availability.

Upgrade PraisonAI Platform to version 0.1.4 or later, which removes the insecure default cryptographic key. Until upgrading, ensure the environment variable PLATFORM_JWT_SECRET is explicitly set to a strong, unique secret in all deployments, and avoid using the default "dev-secret-change-me" value. Additionally, set PLATFORM_ENV to a value other than "dev" in production environments to enable the safety check. Patch status is not explicitly stated as 'official-fix' but version 0.1.4 addresses the issue; therefore, upgrading is the recommended remediation.