CVE-2026-57147: MervinPraison PraisonAI · Use of Hard-coded Credentials
Affects MervinPraison PraisonAISource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 4.6.51 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.6.51, 0.1.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade PraisonAI to 4.6.51; praisonai-platform and mervinpraison/PraisonAI to 0.1.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MervinPraisonPraisonAI | Affected
| Fixed in
|
| MervinPraisonpraisonai-platform | Affected
| Fixed in
|
GitHubmervinpraison/PraisonAIpkg:github/mervinpraison/PraisonAIOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade PraisonAI to version 0.1.6 or later, where this vulnerability is fixed. Ensure that the PLATFORM_JWT_SECRET environment variable is set to a secure, secret value in production environments, and that PLATFORM_ENV is properly configured to enable production guards. No other mitigations are indicated by the vendor advisory.
Description
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.
References
- github.com/MervinPraison/PraisonAI/security/advisories/GHSA-cwj8-7gp2-ggcw (opens in a new tab)
- github.com/MervinPraison/PraisonAI/pull/1793 (opens in a new tab)
- github.com/MervinPraison/PraisonAI/commit/e0fb8e7dd1ee6759c18ed07f436c21dbd9c20747 (opens in a new tab)
- github.com/MervinPraison/PraisonAI/releases/tag/v4.6.51 (opens in a new tab)
- youtube.com/watch?v=bDSRHAI28BY&list=RDhqGkrTbgU2c&index=8 (opens in a new tab)