Advisory record · 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

CVSS 9.8 CriticalCriticalEPSS 0.0045 · 39th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
praisonai-platformPyPI<0.1.40.1.4
Identifiers
GHSA-3qg8-5g3r-79v5 · CVE-2026-47410 · PYSEC-2026-479
Weakness (CWE)
CWE-321 · CWE-798
Published
29 Jun 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The praisonai-platform package before 0.1.4 signs JWTs with a hardcoded default secret, "dev-secret-change-me", when PLATFORM_JWT_SECRET is unset and PLATFORM_ENV is also unset, because the safety check is bypassed by the default value of PLATFORM_ENV. An unauthenticated attacker who knows this public default can forge tokens for any existing user, including workspace owners and admins, and take over those accounts. Upgrade to praisonai-platform 0.1.4 or later, and set PLATFORM_JWT_SECRET to a strong secret in every deployment.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0045, the 39th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:04 UTC First seen by agentprime
  2. 31 Oct 2026, 15:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.