Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-57148 – Authentication Bypass via Hardcoded JWT Secret – PraisonAI Platform ≤ 0.1.4

Be the first to know when new zero-days emerge:

Summary

CVE-2026-57148 is a critical authentication bypass vulnerability in praisonai-platform, the platform/backend component of the PraisonAI multi-agent framework. The service falls back to a hardcoded, publicly known JWT signing secret (dev-secret-change-me) whenever the PLATFORM_JWT_SECRET environment variable is not explicitly set, and the guard meant to block this in production never fires because it only checks PLATFORM_ENV, which itself defaults to "dev". The flaw allows any unauthenticated network attacker to forge valid session tokens and impersonate arbitrary users, including workspace owners, and carries a CVSS v3.1 score of 9.8 (Critical).

Technical details

  • Root cause: auth_service.py in praisonai-platform signs and validates JWTs using a default constant (dev-secret-change-me) when PLATFORM_JWT_SECRET is not configured. A production-safety guard exists but only raises an error when PLATFORM_ENV != "dev"; since PLATFORM_ENV defaults to "dev" and is not set by standard deployment instructions, the guard silently never activates.
  • Trigger conditions: The vulnerability is present in any default deployment of praisonai-platform where operators have not manually set PLATFORM_JWT_SECRET and PLATFORM_ENV to production-safe values — which, per the advisory, describes the vast majority of real-world installs.
  • Attack vector: Network-based, no authentication or user interaction required. An attacker only needs to know (or look up) the publicly disclosed default secret string to mint a valid HS256-signed JWT with an arbitrary sub/email claim.
  • Impact: Full authentication bypass and account takeover, including impersonation of workspace owners/admins. This can lead to unauthorized data access, resource deletion, and eviction of legitimate workspace members — compromising confidentiality, integrity, and availability of the platform.
  • History: This CVE represents an incomplete/regressed fix for an earlier advisory (GHSA-3qg8-5g3r-79v5 / CVE-2026-47410) that had claimed version 0.1.4 as remediated; version 0.1.4 was later found to still contain the same flawed guard logic.

Affected software

  • praisonai-platform (PyPI package): versions 0.1.0 through 0.1.4 (inclusive)
  • Deployments running from the unpatched main branch prior to the fix commit are also affected

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade praisonai-platform to version 0.1.6 or later, which removes reliance on the insecure default secret/guard logic.
  • If immediate patching is not possible:
    • Explicitly set a strong, unique PLATFORM_JWT_SECRET environment variable in every deployment — never allow the application to fall back to its built-in default.
    • Explicitly set PLATFORM_ENV to a non-dev value (e.g., production) in all production and internet-facing deployments so any remaining safety checks are triggered.
    • Rotate all existing JWT secrets and force re-authentication of all users after upgrading, since any tokens forged prior to remediation should be considered compromised.
    • Restrict network exposure of the praisonai-platform authentication endpoints until the upgrade and secret rotation are completed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge