CVE-2026-47410 json
praisonai-platform: JWT signing key defaults to hardcoded "dev-secret-change-me", allowing token forgery for any user when PLATFORM_ENV is unset
published 5mo ago modified 18d ago also EUVD-2026-46324 , GHSA-3qg8-5g3r-79v5 , PYSEC-2026-479
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 39%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi praisonai-platform 0.1.4
- praison praisonai-platform 0.1.4
- github.com/MervinPraison/PraisonAI@ef79b7a commit
- github.com/MervinPraison/PraisonAI#1685 pull request
Is CVE-2026-47410 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 3mo ago
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-3qg8-5g3r-79v5 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | praisonai-platform | <0.1.4 |
0.1.4 |
Affected products
- MervinPraison praisonai-platform
Classification
References
- github.com /MervinPraison/PraisonAI/pull/1685
- github.com /MervinPraison/PraisonAI/commit/ef79b7a0561796ad9807f0f09538c25cc78d3619
-
github.com
/MervinPraison/PraisonAI/security/advisories/GHSA-3qg8-5g3r-79v5
exploit, web
-
github.com
/MervinPraison/PraisonAI
package
-
pypi.org
/project/praisonai-platform
package
-
github.com
/advisories/GHSA-3qg8-5g3r-79v5
advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-47410
advisory
Sources
- CVE List CVE-2026-47410
- GitHub Advisory GHSA-3qg8-5g3r-79v5
- NVD CVE-2026-47410
- OSV PYSEC-2026-479
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.