EUVD-2026-78396
GHSA-f38v-77qj-h4jq
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Signing secret is public in source so PR:N is genuine, not overstated; remote API token forgery (AV:N/AC:L/UI:N) yields full identity takeover (C:H/I:H/A:H).
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
5DescriptionCVE.org
PraisonAI is a multi-agent teams system. Prior to 0.1.6, praisonai_platform/services/auth_service.py falls back to the public dev-secret-change-me HS256 signing key when PLATFORM_JWT_SECRET is unset, while the startup and token-issuance guards are disabled because PLATFORM_ENV also defaults to dev. An unauthenticated attacker can sign a JWT containing an attacker-chosen sub value, and AuthService._verify_token() accepts it as an authenticated identity, enabling user or workspace-owner impersonation when a target identifier is known. This vulnerability is fixed in praisonai-platform 0.1.6.
AnalysisAI
Unauthenticated authentication bypass in praisonai-platform prior to 0.1.6 (and PraisonAI before 4.6.51) allows a remote attacker to forge HS256 session JWTs using the publicly known default signing key 'dev-secret-change-me' and be accepted as any identity the attacker names in the token's sub claim, including a workspace owner. The vulnerable state is the shipped default: the documented startup command sets neither PLATFORM_JWT_SECRET (so the hardcoded fallback is used) nor PLATFORM_ENV (which stays at 'dev', leaving the startup and token-issuance guards default-open). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitable against DEFAULT deployments of praisonai-platform <0.1.6 (and PraisonAI <4.6.51) that do not explicitly export a strong PLATFORM_JWT_SECRET - which the documented startup command (`python -m praisonai_platform --host 0.0.0.0 --port 8000` / uvicorn equivalent) does not, so the vulnerable state is the shipped default rather than an edge case. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | All exploitability signals in the CVSS vector align and are genuinely justified: AV:N (JWT verified over the network API), AC:L (mint a token with any JWT library), PR:N and UI:N (no account, no victim interaction). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: praisonai-platform 0.1.6 (with PraisonAI 4.6.51 for the umbrella package) - upgrade immediately, since 0.1.4 is not a fix despite GHSA-3qg8-5g3r-79v5 previously claiming otherwise; consult https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-f38v-77qj-h4jq and the release notes at https://github.com/MervinPraison/PraisonAI/releases/tag/v4.6.51 for the exact artifacts. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory every deployment of praisonai-platform and PraisonAI, identify those running versions prior to 0.1.6 and 4.6.51 respectively, and upgrade to praisonai-platform 0.1.6 / PraisonAI 4.6.51; where an upgrade cannot be completed immediately, set PLATFORM_JWT_SECRET to a strong randomly generated value, set PLATFORM_ENV to a non-development value so the default-open startup and token-issuance guards close, invalidate all existing sessions and issued tokens, and preserve authentication logs for review. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Wazuh SIEM platform versions 4.4.0 through 4.9.0 contain an unsafe deserialization vulnerability in the DistributedAPI t
BentoML version 1.4.2 and earlier contains an unauthenticated remote code execution vulnerability through insecure deser
pgAdmin 4 contains critical remote code execution vulnerabilities in the Query Tool download and Cloud Deployment endpoi
The renderLocalView function in render/views.py in graphite-web in Graphite 0.9.5 through 0.9.10 uses the pickle Python
BentoML is a Python library for building online serving systems optimized for AI apps and model inference. Rated critica
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
pyLoad download manager version prior to 0.5.0b3.dev77 exposes the Flask SECRET_KEY through an unauthenticated endpoint.
Langflow (a visual LLM pipeline builder) contains a critical unauthenticated code execution vulnerability (CVE-2026-3301
In Mercurial before 4.1.3, "hg serve --stdio" allows remote authenticated users to launch the Python debugger, and conse
Unauthenticated remote code execution affects Kestra OSS (the open-source event-driven orchestration platform) prior to
Unauthenticated remote code execution in Marimo ≤0.20.4 allows attackers to execute arbitrary system commands via the `/
pyLoad is the free and open-source Download Manager written in pure Python. Rated medium severity (CVSS 5.3), this vulne
Same weakness CWE-287 – Improper Authentication
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today