# CVE-2026-40117: PraisonAIAgents Affected by Arbitrary File Read via read_skill_file Missing Workspace Boundary and Approval Gate

> Attackers can read arbitrary files from the filesystem via prompt injection in PraisonAIAgents due to missing workspace boundaries in read_skill_file.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-grrg-5cg9-58pf, PYSEC-2026-2949

## What is CVE-2026-40117?

CVE-2026-40117 is a medium-severity path traversal vulnerability in MervinPraison PraisonAIAgents, published on 9 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PraisonAIAgents is a multi-agent teams system. Prior to 1.5.128, read_skill_file() in skill_tools.py allows reading arbitrary files from the filesystem by accepting an unrestricted skill_path parameter. Unlike file_tools.read_file which enforces workspace boundary confinement, and unlike run_skill_script which requires critical-level approval, read_skill_file has neither protection. An agent influenced by prompt injection can exfiltrate sensitive files without triggering any approval prompt. This vulnerability is fixed in 1.5.128.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-40117?

3 open source packages ship an affected version, including praisonaiagents. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonaiagents` | PyPI | All versions | 1.5.128 |
| `praisonaiagents` | PyPI | All versions | 1.5.128 |
| `praisonaiagents` | PyPI | All versions | 1.5.128 |

Products: Praison Praisonaiagents.

## How do I fix CVE-2026-40117?

Upgrade praisonaiagents to 1.5.128 or later.

## Is CVE-2026-40117 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40117 exists.

## Other vulnerabilities in MervinPraison PraisonAIAgents

- [CVE-2026-34938](https://insights.sbomify.com/CVE-2026-34938/): PraisonAI: Python Sandbox Escape via str Subclass startswith() Override in execute_code (critical 10.0)
- [CVE-2026-40111](https://insights.sbomify.com/CVE-2026-40111/): PraisonAIAgents has an OS Command Injection via shell=True in Memory Hooks Executor (memory/hooks.py) (critical 9.3)
- [CVE-2026-34954](https://insights.sbomify.com/CVE-2026-34954/): PraisonAI: SSRF in FileTools.download_file() via Unvalidated URL (high 8.6)
- [CVE-2026-34937](https://insights.sbomify.com/CVE-2026-34937/): PraisonAI: Shell Injection in run_python() via Unescaped $() Substitution (high 7.8)
- [CVE-2026-44335](https://insights.sbomify.com/CVE-2026-44335/): SSRF bypass in PraisonAI (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40117 and fix it if it is affected.

What it is: CVE-2026-40117 is a medium-severity path traversal vulnerability in MervinPraison PraisonAIAgents, published on 9 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40117 exists.

Affected packages and fixed versions:
- praisonaiagents (PyPI): affected all versions; fixed in 1.5.128
- praisonaiagents (PyPI): affected all versions; fixed in 1.5.128
- praisonaiagents (PyPI): affected all versions; fixed in 1.5.128

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40117/ (Markdown: https://insights.sbomify.com/CVE-2026-40117/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40117
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40117
- OSV: https://osv.dev/vulnerability/CVE-2026-40117

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40117/
Summaries are generated and may contain mistakes; the official description above is the record.