Quick answers
- Is CVE-2026-44334 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44334 being exploited in the wild.
- How severe is CVE-2026-44334?
- High severity, with a CVSS score of 8.4, published 8 May 2026.
- Which products and versions are affected?
- praisonai (PyPI) ECOSYSTEM:introduced=4.5.139,fixed=4.6.32.
- Is there a fix for CVE-2026-44334?
- Yes. praisonai (PyPI): upgrade to 4.6.32 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44334 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44334?
- Check whether you run Praisonai or praisonai (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 (PyPI): upgrade to 4.6.32 or later
pip install "praisonai>=4.6.32"
Technical details
A remote code execution (RCE) vulnerability exists in PraisonAI due to an improper control of code generation (CWE-94) in `praisonai/templates/tool_override.py`. While CVE-2026-40287 introduced an environment variable gate (`PRAISONAI_ALLOW_LOCAL_TOOLS`) to prevent automatic loading of `tools.py`, this specific file was overlooked. An attacker can trigger the vulnerability by sending a POST request to `/v1/recipes/run` with a `recipe` parameter pointing to a malicious GitHub repository or local absolute path. The application uses `spec.loader.exec_module()` to load `tools.py` from the provided recipe directory without authentication or signature verification. This allows for arbitrary Python code execution within the context of the server process. The issue is patched in version 4.6.32.
Affected products
- MervinPraison praisonai >= 4.5.139, <= 4.6.31
Identifiers
- CVE-2026-44334
- GHSA-xcmw-grxf-wjhj
- PYSEC-2026-2926
Timeline
- 2026-04-25: other: Vulnerability confirmed on version 4.6.31
- 2026-04-29: disclosed
- 2026-05-06: advisory
- 2026-05-08: other: NVD published CVE-2026-44334