# CVE-2026-44339: PraisonAI unsafe tool resolution in ToolExecutionMixin

Source: https://junglewise.ai/threats/cve-2026-44339-praisonai-unsafe-tool-resolution-in-toolexecutionmixin  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-08. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

CVE-2026-44339 · Severity: high · CVSS 8.6 · Published 2026-05-08

PraisonAI, a framework for building AI agents, contains a flaw in how it identifies and runs tools. An attacker who can influence the name of a tool being called can trick the system into executing internal functions that were never intended to be accessible. This could allow an unauthorized user to trigger sensitive operations, access internal data, or execute arbitrary code depending on the functions available in the application's memory.

Technologies: [Praisonai](https://junglewise.ai/threats/technologies/praisonai), [Praisonaiagents](https://junglewise.ai/threats/technologies/praisonaiagents), [praisonai (PyPI)](https://junglewise.ai/threats/technologies/pypi-praisonai), [praisonaiagents (PyPI)](https://junglewise.ai/threats/technologies/pypi-praisonaiagents). Vendors: [Praison](https://junglewise.ai/threats/vendors/praison), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-44339 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-44339 being exploited in the wild.

**How severe is CVE-2026-44339?** High severity, with a CVSS score of 8.6, published 8 May 2026.

**Which products and versions are affected?** praisonai (PyPI) ECOSYSTEM:introduced=0,fixed=4.6.37; praisonaiagents (PyPI) ECOSYSTEM:introduced=0,fixed=1.6.37.

**Is there a fix for CVE-2026-44339?** Yes. praisonai (PyPI): upgrade to 4.6.37 or later; praisonaiagents (PyPI): upgrade to 1.6.37 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-44339 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-44339?** 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.6.37 or later

  ```sh
  pip install "praisonai>=4.6.37"
  ```

- praisonaiagents (PyPI): upgrade to 1.6.37 or later

  ```sh
  pip install "praisonaiagents>=1.6.37"
  ```


## Technical details

The vulnerability exists in the `ToolExecutionMixin.execute_tool` method within `praisonaiagents`. When a tool name is requested that does not match a declared tool or a registry entry, the code falls back to searching `globals()` and the `__main__` module. Because the default agent configuration sets `_perm_allow` to `None` (effectively an 'allow all' policy), any callable found in these scopes can be executed with attacker-supplied arguments. This allows for the invocation of unintended application callables, potentially leading to remote code execution or unauthorized state changes if privileged helper functions are present in the process scope. The issue is fixed in versions 4.6.37 (PraisonAI) and 1.6.37 (praisonaiagents).

## Affected products

- MervinPraison PraisonAI <= 4.6.36
- MervinPraison praisonaiagents <= 1.6.36

## Identifiers

- CVE-2026-44339
- GHSA-gmjg-hv98-qggq
- PYSEC-2026-2915
- PYSEC-2026-2948

## Timeline

- 2026-05-08: kev added: NVD published date
- 2026-05-11: advisory: GitHub Advisory published

## References

- [https://api.github.com/users/shmulc8](https://api.github.com/users/shmulc8)
- [https://github.com/shmulc8](https://github.com/shmulc8)
- [https://api.github.com/users/shmulc8/gists%7B/gist_id%7D](https://api.github.com/users/shmulc8/gists%7B/gist_id%7D)
- [https://api.github.com/users/shmulc8/repos](https://api.github.com/users/shmulc8/repos)
- [https://avatars.githubusercontent.com/u/34924662?v=4](https://avatars.githubusercontent.com/u/34924662?v=4)
- [https://api.github.com/users/shmulc8/events%7B/privacy%7D](https://api.github.com/users/shmulc8/events%7B/privacy%7D)

## Related threats

- [PraisonAI authentication bypass in A2U event streaming](https://junglewise.ai/threats/cve-2026-57146-praisonai-a2u-incomplete-authentication-fix-leaves-current-serve)
- [PraisonAI sandbox escape when Landlock unavailable](https://junglewise.ai/threats/cve-2026-57144-praisonai-sandlocksandbox-falls-back-to-unrestricted-subprocess)
- [PraisonAI recipe policy bypass via YAML-approved tools](https://junglewise.ai/threats/cve-2026-57142-praisonai-recipe-workflow-policy-can-be-bypassed-by-declaring-and)
- [PraisonAI shell command injection in compute-bridged file tools](https://junglewise.ai/threats/cve-2026-57117-praisonai-compute-bridged-file-tools-allow-shell-command)
- [PraisonAI AgentOS authentication bypass in FastAPI deployment](https://junglewise.ai/threats/cve-2026-57116-praisonai-agentos-remains-unauthenticated-after-incomplete-fix)