cve.bz

CVE-2026-47410 mervinpraison praisonai-platform: Use of Hard-coded Cryptographic Key

9.8 criticalEPSS 0.4%Fix available

Critical (9.8) in mervinpraison praisonai-platform. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in praisonai-platform 0.1.4.

On this page
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.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2026-07-22. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-321 Use of Hard-coded Cryptographic Key
CWE-798 Use of Hard-coded Credentials
OWASP Top 10
A04:2025 Cryptographic Failures, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • praisonai-platform (PyPI): fixed in 0.1.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-47410 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-47410?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-47410?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-47410 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
MervinPraison praisonai-platform< 0.1.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3qg8-5g3r-79v5PyPIpraisonai-platform<0.1.40.1.4
PYSEC-2026-479PyPIpraisonai-platform<0.1.40.1.4

Attack patterns (CAPEC)

  • CAPEC-70 Try Common or Default Usernames and Passwords Likelihood: Medium · Severity: High
  • CAPEC-191 Read Sensitive Constants Within an Executable Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON