PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

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

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

Summary

CVE-2026-57147 is a critical authentication bypass vulnerability in the praisonai-platform package (the backend platform component of the PraisonAI multi-agent framework). The platform’s authentication service ships with a hardcoded default JWT signing secret, "dev-secret-change-me", which is used to both sign and verify Bearer tokens. Because the safeguard meant to block this default in production only activates under a condition that most real-world deployments never trigger, an unauthenticated remote attacker can forge valid JWTs and impersonate any user, including workspace owners and administrators — earning this issue a maximum-severity CVSS score of 9.8.

Technical details

  • Root cause: praisonai_platform/services/auth_service.py defines a static, publicly known fallback secret ("dev-secret-change-me") used for HMAC-SHA256 JWT signing and verification when PLATFORM_JWT_SECRET is not explicitly configured.
  • Flawed guard logic: A check exists intended to reject the default secret in production, but it only fires when PLATFORM_ENV is explicitly set to a value other than "dev". Since PLATFORM_ENV itself defaults to "dev" when left unset, deployments that configure neither variable silently remain in the vulnerable state.
  • Trigger conditions: Any deployment of praisonai-platform that does not explicitly set PLATFORM_JWT_SECRET (and, due to the guard flaw, also does not explicitly set PLATFORM_ENV) runs with the known default signing key active.
  • Attack vector: Network, no authentication or user interaction required. An attacker who knows the public default secret can craft a JWT with arbitrary sub/email/role claims and present it as a valid Bearer token to any API route protected by the platform’s authentication middleware.
  • Impact: Full authentication bypass and account takeover — attackers can impersonate any existing user, including administrators, gaining unauthorized access to workspace management, project handling, and user access-control functions. All three impact categories (confidentiality, integrity, availability) are rated High.

Affected software

  • praisonai-platform (PyPI package) — versions ≤ 0.1.4

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.5 or later, where the insecure default-initialization logic has been corrected.
  • If immediate patching is not possible:
    • Explicitly set a strong, unique, randomly generated value for the PLATFORM_JWT_SECRET environment variable in every deployment — never rely on the built-in default.
    • Explicitly set PLATFORM_ENV to a non-development value (e.g., production) in production deployments to avoid unintentionally falling back to development behavior.
    • Restrict network exposure of the platform’s API endpoints to trusted networks until the environment variables above are verified as correctly configured.
    • After remediation, rotate any tokens/sessions issued under the default secret, as they should be considered compromised.

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