Unrated

Authentication Bypass in praisonai-platform via Hardcoded Default JWT Secret

IdentifiersCVE-2026-57148CWE-798

CVE-2026-57148 is an improper authentication vulnerability in praisonai-platform caused by use of a hardcoded default JWT signing secret together with a production configuration that remains permissive by default. In affected default deployments, if the platform secret is unset or left at the known default value, an attacker can generate forged JWTs that are accepted as valid by the application. Because the forged tokens can encode arbitrary user identity and authorization context, the flaw enables authentication bypass and impersonation of legitimate users, including high-privilege workspace owners. The issue stems from insecure default credential material and insufficient fail-closed validation around JWT secret configuration in production deployments.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to bypass authentication entirely by forging valid JWTs. This enables impersonation of arbitrary users and can result in full compromise of affected workspaces, including unauthorized read, update, and delete operations; abuse of member and role management functions; workspace takeover or deletion; and lockout of legitimate users. Where privileged identities are impersonated, the attacker can effectively obtain administrative control within the application’s trust boundary.

Mitigation

If you can’t patch tonight, do this now.

Explicitly configure PLATFORM_JWT_SECRET to a strong, unique secret in every deployment and verify this during startup. Do not permit operation when the secret is missing or set to the insecure default value. Do not rely on environment-mode defaults to secure production behavior. As a temporary defensive measure, enforce deployment or startup checks that block service initialization unless a non-default secret is present, and review token issuance and verification paths for consistent secret handling.

Remediation

Patch, then assume compromise.

Upgrade praisonai-platform to version 0.1.6 or later. Remove reliance on any hardcoded default JWT secret and ensure the application fails closed whenever the platform JWT secret is unset or matches the known insecure default. Apply the same validation consistently across all code paths that issue, sign, or verify tokens. After remediation, rotate the JWT secret and invalidate previously issued tokens to prevent continued use of forged or legacy tokens generated under the insecure configuration.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

PraisonAIPraisonai-Platformapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

1 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1