CVE-2026-47410

praisonai-platform: JWT signing key defaults to hardcoded "dev-secret-change-me", allowing token forgery for any user when PLATFORM_ENV is unset

Published Jul 21, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

PraisonAI Platform versions prior to 0.1.4 use a hard‑coded JWT signing secret of "dev‑secret‑change‑me" whenever the environment variable PLATFORM_JWT_SECRET is not set. A safety check that would normally trigger when the signing key is the default only executes if PLATFORM_ENV is not equal to "dev", but the default value for that variable is "dev", meaning the check is bypassed silently in any deployment that does not explicitly change the environment. An attacker who can read the source file or repository can therefore construct a valid JWT with arbitrary "sub" and "email" claims, authenticating as any user, including workspace owners and administrators. This flaw represents a critical authentication bypass caused by improper key management (CWE-321, CWE-798).

Affected Systems

The affected software is the PraisonAI Platform developed by MervinPraison. Versions earlier than 0.1.4 of the platform include the default hard‑coded JWT signing key. The vulnerability is present when the deployment does not specify the PLATFORM_JWT_SECRET or explicitly sets PLATFORM_ENV to "dev". The issue was addressed in version 0.1.4, which replaces the default key with proper configuration enforcement.

Risk and Exploitability

The severity is critical, with a CVSS score of 9.8, and the EPSS score is below 1%, indicating that widespread exploitation has not yet been observed. Because the flaw is tied to a hard‑coded default key that is easy to discover in the source repository, an attacker can exploit it in any deployment that fails to override the defaults. The vulnerability does not depend on elevated privileges, so any adversary with access to the application code or the ability to read the repo can forge tokens. The issue is not currently listed in CISA’s KEV catalog, but its high CVSS and widespread code availability make it a priority for remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the platform to version 0.1.4 or newer.
  • Configure the environment variable PLATFORM_JWT_SECRET with a strong, random secret before starting the service.
  • Set PLATFORM_ENV to a value other than "dev" (e.g., "production") so that the safety check activates and prevents the use of the hard‑coded key.

Generated by OpenCVE AI on July 30, 2026 at 17:04 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-3qg8-5g3r-79v5 praisonai-platform: JWT signing key defaults to hardcoded "dev-secret-change-me", allowing token forgery for any user when PLATFORM_ENV is unset
History
Type Values Removed Values Added
First Time appeared Mervinpraison
Mervinpraison praisonai
Vendors & Products Mervinpraison
Mervinpraison praisonai
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title praisonai-platform: JWT signing key defaults to hardcoded "dev-secret-change-me", allowing token forgery for any user when PLATFORM_ENV is unset
Weaknesses CWE-321
CWE-798
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key

  • CWE-798

    Use of Hard-coded Credentials

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 22, 2026, 2:43 PM
Reserved
May 19, 2026, 7:37 PM
Status
Deferred
Published
Jul 21, 2026, 5:17 PM
Modified
Oct 24, 2026, 7:10 PM