External risk intelligence

PraisonAI Platform Insecure Default JWT Secret Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-47410

The vulnerability exists in the PraisonAI Platform, which functions as a multi-agent system platform. Such platforms are commonly deployed as web applications or API services to enable external agent communication and management, making them likely to be reachable from the internet in typical deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the PraisonAI Platform could allow unauthorized access to user accounts, including administrative roles, due to an insecure default cryptographic key. This affects systems that have not updated to version 0.1.4 or later, potentially exposing sensitive data and system functions to attackers. The main concern is confirming relevance and exposure.

Insecure default key allows account takeover.
Critical systems at risk without explicit configuration.
Confirm if this platform is in use and exposed.

Attack Path

How an attacker could exploit the issue

An attacker can gain access to sensitive information by exploiting a hardcoded cryptographic key within the PraisonAI Platform. This key, used for signing JSON Web Tokens (JWTs), defaults to an easily discoverable value, `dev-secret-change-me`. Since a safety check is bypassed by default, an attacker can read this key from public source files, create a forged JWT, and authenticate as any user, including administrators, leading to unauthorized access and control.

Exposure of a default, hardcoded secret.
Crafting a malicious JWT to bypass authentication.
Unauthorized access and administrative control.

Live Threat

Current exploitation, exposure, and threat context

When the PraisonAI Platform is deployed without explicitly setting the `PLATFORM_ENV` to a value other than "dev", an attacker can leverage a hardcoded cryptographic key to forge authentication tokens. This could allow them to impersonate any user, including administrators, by crafting JWTs with arbitrary claims.

User and system data could be compromised.
An attacker could forge JWTs to impersonate users.
Unauthorized access to user accounts and data may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

The PraisonAI Platform's default JWT secret requires immediate attention from platform and security teams. The first step is to inventory all PraisonAI Platform deployments, confirm their network exposure and business criticality, and identify the accountable system owners. This will inform a risk-based remediation plan, which may involve coordinating with the vendor for updates or implementing compensating controls.

Platform and security teams own this.
Verify all PraisonAI Platform instances.
Plan vendor-coordinated updates.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the PraisonAI Platform?

The PraisonAI Platform serves as the underlying framework for multi-agent systems, providing the infrastructure to manage and orchestrate automated agents. It is typically used as a web-based service or API layer to facilitate communication and task delegation across these agents, acting as the centralized hub for system logic and workspace management.

How does CVE-2026-47410 impact authentication?

This vulnerability involves the use of hardcoded credentials, specifically a static cryptographic key used to sign JSON Web Tokens (JWTs). Because this default secret is publicly known, the system fails to correctly verify the identity of users. An attacker can use this known key to manually create forged authentication tokens, effectively bypassing the login process and masquerading as any user, including high-privilege administrators.

Does this vulnerability trigger if I use custom settings?

The bug specifically triggers when the platform uses its default environment configuration. If you have explicitly updated the environment settings to a production mode—meaning you are not running in the default 'dev' environment—the safety mechanism meant to prevent this issue is enabled. The vulnerability is active primarily in deployments that rely on the software's initial, unconfigured state.

Is my deployment at risk according to Halo Surface Signal?

Halo Surface Signal notes that because the PraisonAI Platform is often deployed as a web application or API service to handle external agent communication, it is frequently reachable from the internet. If your instance is accessible to the public internet, it falls into the category of higher-risk deployments, as remote attackers can easily reach the platform to attempt token forgery.

What is the first step to remediate this issue?

The immediate priority is to identify and inventory all instances of the PraisonAI Platform running in your environment to understand your total footprint. Once located, verify the version currently in use; if you are running any version prior to 0.1.4, you should update to the patched version immediately to remove the hardcoded secret and restore secure authentication.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.