PraisonAI is a multi-agent teams system. Prior to 0.1.6, praisonai_platform/services/auth_service.py assigns the public dev-secret-change-me value to JWT_SECRET when PLATFORM_JWT_SECRET is unset, and its production guard does not run when PLATFORM_ENV is also unset because that setting defaults to dev. A remote unauthenticated attacker can mint an HS256 token with an arbitrary sub and email, and the platform's AuthService._verify_token() and get_current_user dependency accept the forged identity for protected API routes. This vulnerability is fixed in praisonai-platform 0.1.6.
CVE-2026-57147
CRITICALPre-NVD 9.89.8—Elevated
EchelonGraph scoreMEDIUM confidence
This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 46% 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).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0
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
- 54%
- KEV
- Not listed
Published
June 18, 2026
Last Modified
September 17, 2026
Advisory Details (5)
Auto-updated Sep 17, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_pr, github_release.
github Patch Available🟡 PoC Available
praisonai-platform: default JWT signing secret 'dev-secret-change-me' enables token forgery (CWE-798) · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-cwj8-7gp2-ggcwgithub_release Patch Available
PraisonAI v4.6.51
Patch available: MervinPraison/PraisonAI v4.6.51
https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.51github_pr Patch Available
fix: harden JWT secret defaults and replace eval() in examples (GHSA-3qg8-5g3r-79v5, GHSA-vg22-4gmj-prxw)
Patch available: MervinPraison/PraisonAI v4.6.144 (PR #1793 merged 2026-06-02)
https://github.com/MervinPraison/PraisonAI/pull/1793github_commit Patch Available
commit e0fb8e7dd1ee (MervinPraison/PraisonAI)
Patch available: MervinPraison/PraisonAI v4.6.144 (contains commit e0fb8e7dd1ee)
https://github.com/MervinPraison/PraisonAI/commit/e0fb8e7dd1ee6759c18ed07f436c21dbd9c20747Vendor Advisories for CVE-2026-57147(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 | 0.1.6 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× 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-18 19:28 UTCEPSS rescore
- 2026-09-17 19:31 UTCEPSS rescore
- 2026-09-17 15:30 UTCEG score recompute
- 2026-09-17 14:35 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 11:29 UTCEG score recompute
- 2026-07-30 22:29 UTCEG score recompute
- 2026-07-26 17:44 UTCEG score recompute
- 2026-07-23 03:20 UTCEG score recompute
- 2026-07-20 21:33 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-798
Frequently asked(5)
What is CVE-2026-57147?
CVE-2026-57147 is a critical vulnerability published on June 18, 2026. PraisonAI is a multi-agent teams system. Prior to 0.1.6, praisonaiplatform/services/authservice.py assigns the public dev-secret-change-me value to JWTSECRET when PLATFORMJWTSECRET is unset, and its production guard does not run when PLATFORMENV is also unset because that setting defaults to dev. A…
When was CVE-2026-57147 disclosed?
CVE-2026-57147 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57147 actively exploited?
CVE-2026-57147 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.8% of all scored CVEs.
What is the CVSS score of CVE-2026-57147?
CVE-2026-57147 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-57147?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57147, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57147
Is Your Infrastructure Affected by CVE-2026-57147?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.