Quick answers
- Is CVE-2026-57117 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57117 being exploited in the wild.
- How severe is CVE-2026-57117?
- High severity, with a CVSS score of 8.8, published 23 October 2026.
- Which products and versions are affected?
- MervinPraison PraisonAI 4.6.10 to 4.6.57; praisonai (PyPI) ECOSYSTEM:introduced=4.6.10,fixed=4.6.59.
- Is there a fix for CVE-2026-57117?
- Yes. praisonai (PyPI): upgrade to 4.6.59 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57117 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-57117?
- Check whether you run MervinPraison 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.59 or later
pip install "praisonai>=4.6.59"
Technical details
The LocalManagedAgent and SandboxedAgent compute bridging layer wraps file operations (read_file, list_files, write_file) by constructing shell command strings with raw path arguments, then executing them via subprocess or Docker. An attacker who can influence a path argument can break out of the quoted path using shell metacharacters (e.g., `"; command; #`) to execute arbitrary shell commands. The vulnerability affects versions 4.6.10 through 4.6.57, and is fixed in 4.6.59.
Affected products
- MervinPraison PraisonAI 4.6.10 to 4.6.57
Identifiers
- CVE-2026-57117
- GHSA-w6h2-fr4q-xvxv
- PYSEC-2026-3522
Timeline
- 2026-06-17: disclosed: GitHub Security Advisory published
- 2026-10-23: patched: Fix released in version 4.6.59