Is CVE-2026-40288 exploited in the wild?

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

How severe is CVE-2026-40288?

Critical severity, with a CVSS score of 9.8, published 14 April 2026.

Which products and versions are affected?

praisonai (PyPI) ECOSYSTEM:introduced=0,fixed=4.5.139; praisonaiagents (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.140.

Is there a fix for CVE-2026-40288?

Yes. praisonai (PyPI): upgrade to 4.5.139 or later; praisonaiagents (PyPI): upgrade to 1.5.140 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-40288 attacked?

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

Am I affected by CVE-2026-40288?

Check whether you run Praisonai, Praisonaiagents, praisonai (PyPI) or one of the others listed 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-40288: MervinPraison PraisonAI RCE via job workflow YAML

CVE-2026-40288 · Severity: critical · CVSS 9.8 · Published 2026-04-14

PraisonAI, an AI agent and workflow framework, is vulnerable to a critical security flaw that allows for remote code execution. By providing a specially crafted workflow file, an attacker can force the system to execute arbitrary commands or Python scripts on the host machine. This could lead to a total takeover of the server or development environment where the software is running.

Technologies: Praisonai, Praisonaiagents, praisonai (PyPI), praisonaiagents (PyPI). Vendors: Praison, PyPI.

Quick answers

Is CVE-2026-40288 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40288 being exploited in the wild.
How severe is CVE-2026-40288?: Critical severity, with a CVSS score of 9.8, published 14 April 2026.
Which products and versions are affected?: praisonai (PyPI) ECOSYSTEM:introduced=0,fixed=4.5.139; praisonaiagents (PyPI) ECOSYSTEM:introduced=0,fixed=1.5.140.
Is there a fix for CVE-2026-40288?: Yes. praisonai (PyPI): upgrade to 4.5.139 or later; praisonaiagents (PyPI): upgrade to 1.5.140 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-40288 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-40288?: Check whether you run Praisonai, Praisonaiagents, praisonai (PyPI) or one of the others listed 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 (PyPI): upgrade to 4.5.139 or later
```
pip install "praisonai>=4.5.139"
```
praisonaiagents (PyPI): upgrade to 1.5.140 or later
```
pip install "praisonaiagents>=1.5.140"
```

Technical details

A remote code execution (RCE) vulnerability exists in PraisonAI due to the unsafe execution of commands defined in YAML workflow files. When a workflow with 'type: job' is processed, the JobWorkflowExecutor in 'job_workflow.py' uses subprocess.run() for 'run' keys, exec() for 'script' keys, and direct execution for 'python' keys without sufficient sanitization or sandboxing. An attacker can provide a malicious YAML file to achieve arbitrary command execution on the host. The vulnerability is addressed in PraisonAI version 4.5.139 and praisonaiagents version 1.5.140.

Affected products

MervinPraison PraisonAI <= 4.5.138
MervinPraison praisonaiagents <= 1.5.139

Identifiers

CVE-2026-40288
GHSA-vc46-vw85-3wvm
PYSEC-2026-477
PYSEC-2026-488

Timeline

2026-04-10: disclosed
2026-04-10: advisory
2026-04-10: patched: Fixed in PraisonAI 4.5.139 and praisonaiagents 1.5.140

References

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