CVE-2026-47410
Received Received - Intake

Hard-Coded JWT Secret in PraisonAI Platform

Publication date: 2026-07-21

Last updated on: 2026-07-21

Assigner: GitHub, Inc.

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-21
Last Modified
2026-07-21
Generated
2026-07-21
AI Q&A
2026-07-21
EPSS Evaluated
N/A
NVD
CVE-2026-47410
EUVD
EUVD-2026-46324

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
praisonai praisonai_platform to 0.1.4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-321 The product uses a hard-coded, unchangeable cryptographic key.
CWE-798 The product contains hard-coded credentials, such as a password or cryptographic key.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-47410 is a critical flaw in the PraisonAI Platform where the JWT signing secret defaults to a hardcoded value, 'dev-secret-change-me,' when the PLATFORM_JWT_SECRET environment variable is unset. The safety check to prevent this only activates when PLATFORM_ENV is not 'dev,' but the default value is 'dev,' bypassing the check in most deployments. Attackers can forge authentication tokens to impersonate any user, including administrators.

The vulnerability exists because the system fails open by default, allowing the hardcoded secret to be used without explicit opt-in. This enables attackers to mint JWT tokens with arbitrary user claims and gain full account takeover capabilities without prior authentication.

Detection Guidance

Check if the PraisonAI Platform is using the default JWT secret by inspecting environment variables or configuration files for PLATFORM_JWT_SECRET. If unset, verify if PLATFORM_ENV is set to 'dev' which bypasses the safety check. Search for the hardcoded secret 'dev-secret-change-me' in source files or logs.

Impact Analysis

This vulnerability allows attackers to impersonate any user, including administrators, by forging JWT tokens. They can gain unauthorized access to accounts, perform actions on behalf of other users, and potentially take over entire workspaces. The impact includes data breaches, unauthorized modifications, and loss of control over user accounts.

Compliance Impact

This vulnerability likely violates compliance requirements such as GDPR and HIPAA, which mandate strict access controls and protection of sensitive data. Unauthorized access through forged tokens could lead to data breaches, exposing personal or health information. Organizations may face legal penalties, reputational damage, and loss of trust due to non-compliance.

Mitigation Strategies

Upgrade PraisonAI Platform to version 0.1.4 or later. Set a strong, unique PLATFORM_JWT_SECRET environment variable. Change PLATFORM_ENV from 'dev' to a production value if applicable. Ensure the safety check is enforced by failing-closed when the secret is unset.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-47410. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart