PraisonAI command execution in compute-backed file tools
MervinPraison PraisonAI
MervinPraison PraisonAI
| Product | Affected | Fixed in |
|---|---|---|
| praisonai PyPI |
|
|
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.
From the CVE record · GitHub_M
PraisonAI's file-tool compute bridge passes raw path arguments into shell commands when a compute provider is attached. An attacker who can influence a file-tool path can execute arbitrary commands on the host with local compute, or in the container with Docker compute. The input does not specify authentication or user-interaction requirements.
Engineers running the PyPI praisonai package versions 4.6.10 through 4.6.58 should check their deployments.