---
id: "CVE-2026-57117"
kind: "vulnerability"
aliases: ["CVE-2026-57117"]
title: "PraisonAI: file tools let attackers run shell commands on hosts"
severity: "high"
cvss: 8.8
epss: 0.00567
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-agents", "ai-tooling", "praisonai", "python", "self-hosted"]
not_affected_if: ["no-compute-provider-attached", "version-4.6.59-or-later"]
published_at: "2026-10-23T13:17:10+00:00"
first_seen_at: "2026-10-23T21:57:33+00:00"
updated_at: "2026-10-25T12:38:50+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-57117", "first_seen_at": "2026-10-23T21:57:33+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-57117", "first_seen_at": "2026-10-25T12:38:50+00:00"}]
---

# PraisonAI: file tools let attackers run shell commands on hosts

PraisonAI's compute bridge builds shell command strings from raw file-tool path arguments, so a crafted path can break out of its quotes. An attacker who controls that path can run arbitrary shell commands in the compute environment, on the host with compute="local" or inside the container with Docker.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

Check whether the installed praisonai version is from 4.6.10 up to but not including 4.6.59. Check whether LocalManagedAgent or SandboxedAgent is used with a compute provider attached.

## Fix

Upgrade praisonai to 4.6.59 or later.

## Timeline

- 2026-10-23T21:57:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-57117
- 2026-10-25T12:38:50+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-57117

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_