CVE-2026-47410: CWE-321: Use of Hard-coded Cryptographic Key in MervinPraison praisonai-platform
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an insecure default cryptographic key. The JWT signing secret defaults to the hardcoded literal `"dev-secret-change-me"` when `PLATFORM_JWT_SECRET` is unset. A safety check exists but only fires when `PLATFORM_ENV != "dev"`; the default value of `PLATFORM_ENV` is `"dev"`, so the check is silently bypassed in any deployment that does not explicitly opt out. The attacker reads the literal from this public source file, mints a JWT with arbitrary `sub` and `email` claims, and authenticates as any existing user (including workspace owners and admins). PraisonAI Platform version 0.1.4 patches the issue.
AI Analysis
Technical Summary
The PraisonAI Platform before version 0.1.4 contains a critical vulnerability (CVE-2026-47410) due to the use of a hardcoded cryptographic key for JWT signing. When the environment variable PLATFORM_JWT_SECRET is not set, the system defaults to the literal key "dev-secret-change-me". The platform includes a safety check that disables this default key only if PLATFORM_ENV is not set to "dev"; however, since the default PLATFORM_ENV is "dev", this check is effectively bypassed in typical deployments. An attacker can exploit this by reading the hardcoded key from the public source, forging JWT tokens with arbitrary subject and email claims, and gaining unauthorized access as any user, including workspace owners and administrators. The vulnerability is addressed in PraisonAI Platform version 0.1.4.
Potential Impact
Exploitation allows an unauthenticated attacker to forge JWT tokens and impersonate any user, including privileged roles such as workspace owners and administrators. This leads to complete compromise of user authentication and authorization, resulting in full confidentiality, integrity, and availability impact on the affected system.
Mitigation Recommendations
Upgrade to PraisonAI Platform version 0.1.4 or later, where the hardcoded cryptographic key issue is patched. Until upgraded, ensure that the environment variable PLATFORM_JWT_SECRET is explicitly set to a secure, unique secret in all deployments, and avoid using the default "dev" environment setting in production.
CVE-2026-47410: CWE-321: Use of Hard-coded Cryptographic Key in MervinPraison praisonai-platform
Description
PraisonAI Platform is the platform layer for the PraisonAI multi-agent teams system. Versions prior to 0.1.4 have an insecure default cryptographic key. The JWT signing secret defaults to the hardcoded literal `"dev-secret-change-me"` when `PLATFORM_JWT_SECRET` is unset. A safety check exists but only fires when `PLATFORM_ENV != "dev"`; the default value of `PLATFORM_ENV` is `"dev"`, so the check is silently bypassed in any deployment that does not explicitly opt out. The attacker reads the literal from this public source file, mints a JWT with arbitrary `sub` and `email` claims, and authenticates as any existing user (including workspace owners and admins). PraisonAI Platform version 0.1.4 patches the issue.
CVSS v3.1
Score 9.8critical
Affected software
pkg:github/mervinpraison/PraisonAIRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The PraisonAI Platform before version 0.1.4 contains a critical vulnerability (CVE-2026-47410) due to the use of a hardcoded cryptographic key for JWT signing. When the environment variable PLATFORM_JWT_SECRET is not set, the system defaults to the literal key "dev-secret-change-me". The platform includes a safety check that disables this default key only if PLATFORM_ENV is not set to "dev"; however, since the default PLATFORM_ENV is "dev", this check is effectively bypassed in typical deployments. An attacker can exploit this by reading the hardcoded key from the public source, forging JWT tokens with arbitrary subject and email claims, and gaining unauthorized access as any user, including workspace owners and administrators. The vulnerability is addressed in PraisonAI Platform version 0.1.4.
Potential Impact
Exploitation allows an unauthenticated attacker to forge JWT tokens and impersonate any user, including privileged roles such as workspace owners and administrators. This leads to complete compromise of user authentication and authorization, resulting in full confidentiality, integrity, and availability impact on the affected system.
Mitigation Recommendations
Upgrade to PraisonAI Platform version 0.1.4 or later, where the hardcoded cryptographic key issue is patched. Until upgraded, ensure that the environment variable PLATFORM_JWT_SECRET is explicitly set to a secure, unique secret in all deployments, and avoid using the default "dev" environment setting in production.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-19T19:37:43.525Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5fa8792a4a8d59897734f5
Added to database: 07/21/2026, 17:12:25 UTC
Last enriched: 07/21/2026, 17:26:41 UTC
Last updated: 07/21/2026, 21:03:14 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.