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.
CVE-2026-47410
This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(medium)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 48%
- KEV
- Not listed
Published
May 29, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Aug 29, 2026praisonai-platform: JWT signing key defaults to hardcoded "dev-secret-change-me", allowing token forgery for any user when PLATFORM_ENV is unset · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-3qg8-5g3r-79v5refactor: security batch 2 — platform IDOR and deploy hardening
Patch available: MervinPraison/PraisonAI v4.6.140 (PR #1685 merged 2026-05-19)
https://github.com/MervinPraison/PraisonAI/pull/1685commit ef79b7a05617 (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.140 (contains commit ef79b7a05617)
https://github.com/MervinPraison/PraisonAI/commit/ef79b7a0561796ad9807f0f09538c25cc78d3619Vendor Advisories for CVE-2026-47410(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| praisonai-platform | 0.1.0, 0.1.1, 0.1.2, 0.1.3 | 0.1.4 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 41× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 04:08 UTCEG score recompute
- 2026-08-23 14:03 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 00:33 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 01:37 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 10:24 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:58 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 15:02 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:23 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
Show 44 moreShow fewer
- 2026-08-15 16:50 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 00:26 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 17:51 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 15:59 UTCEG score recompute
- 2026-08-11 03:44 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 14:23 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 18:03 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 17:21 UTCEG score recompute
- 2026-08-06 16:59 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-05 20:41 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 22:58 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 15:54 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 06:42 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 13:53 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 05:51 UTCEG score recompute
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 11:32 UTCEG score recompute
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-28 04:01 UTCEG score recompute
- 2026-07-27 03:10 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-29 23:13 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-798 · CWE-321
Frequently asked(5)
What is CVE-2026-47410?
When was CVE-2026-47410 disclosed?
Is CVE-2026-47410 actively exploited?
What is the CVSS score of CVE-2026-47410?
How do I remediate CVE-2026-47410?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47410
Is Your Infrastructure Affected by CVE-2026-47410?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.