Is CVE-2026-47410 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47410 being exploited in the wild.

How severe is CVE-2026-47410?

Critical severity, with a CVSS score of 9.8, published 21 July 2026.

Which products and versions are affected?

praisonai-platform (PyPI) <= 0.1.2, ECOSYSTEM:introduced=0,fixed=0.1.4.

Is there a fix for CVE-2026-47410?

Yes. praisonai-platform (PyPI): upgrade to 0.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47410 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47410?

Check whether you run praisonai-platform (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47410: MervinPraison PraisonAI Platform hardcoded JWT secret

Q: Is there a fix for CVE-2026-47410?

Yes. praisonai-platform (PyPI): upgrade to 0.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47410 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-47410?

Check whether you run praisonai-platform (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47410 · Severity: critical · CVSS 9.8 · Published 2026-07-21

PraisonAI Platform, a system for managing multi-agent AI teams, contains a security flaw where it uses a publicly known, hardcoded password to secure user login tokens by default. Because this "secret" key is available in the public source code, an attacker can create their own fake login credentials. This allows them to bypass security entirely and log in as any user, including administrators, gaining full access to sensitive data and AI workspaces.

Technologies: praisonai-platform (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-47410 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47410 being exploited in the wild.
How severe is CVE-2026-47410?: Critical severity, with a CVSS score of 9.8, published 21 July 2026.
Which products and versions are affected?: praisonai-platform (PyPI) <= 0.1.2, ECOSYSTEM:introduced=0,fixed=0.1.4.
Is there a fix for CVE-2026-47410?: Yes. praisonai-platform (PyPI): upgrade to 0.1.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47410 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47410?: Check whether you run praisonai-platform (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

praisonai-platform (PyPI): upgrade to 0.1.4 or later
```
pip install "praisonai-platform>=0.1.4"
```

Technical details

The PraisonAI Platform's authentication service (auth_service.py) uses a hardcoded literal `_DEFAULT_SECRET = "dev-secret-change-me"` for JWT signing when the `PLATFORM_JWT_SECRET` environment variable is unset. While a safety check exists to prevent the use of this default secret, the check only triggers if `PLATFORM_ENV` is explicitly set to something other than "dev". Since `PLATFORM_ENV` defaults to "dev", the safety check is bypassed in standard deployments. An unauthenticated remote attacker can use the publicly known secret to mint JWTs with arbitrary 'sub' and 'email' claims, granting them full administrative access to the platform. This issue is resolved in version 0.1.4 by hardening the default configuration.

Affected products

MervinPraison PraisonAI Platform < 0.1.4

Identifiers

CVE-2026-47410
GHSA-3qg8-5g3r-79v5
PYSEC-2026-479

Timeline

2026-05-19: patched: Fix merged in commit ef79b7a
2026-07-21: disclosed: CVE-2026-47410 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.