# CVE-2026-47394: PraisonAI vulnerable to unauthenticated arbitrary file read via MCP workflow.show, workflow.validate, deploy.validate

> Unauthenticated attackers can read arbitrary files on the host via path traversal in PraisonAI MCP workflow handlers.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-9cr9-25q5-8prj, PYSEC-2026-2908

## What is CVE-2026-47394?

CVE-2026-47394 is a high-severity path traversal vulnerability in MervinPraison PraisonAI, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PraisonAI is a multi-agent teams system. Prior to version 4.6.40, the fix for GHSA-9mqq-jqxf-grvw / CVE-2026-44336 is incomplete. The original advisory description named four vulnerable handlers in `mcp_server/adapters/cli_tools.py`. Commit `68cc9427` ("fix(security): harden MCP rules path handling…") added a `_resolve_rule_path()` helper and applied it to `rules.create`, `rules.show`, and `rules.delete`. `workflow.show` was left unchanged. Two adjacent handlers in the same file have the same pattern, `workflow.validate` and `deploy.validate`. Neither was mentioned in the original advisory. Both remained  unchanged. The original advisory also identified the dispatcher (`server.py:281-298`) as a root cause. It accepts unvalidated `**kwargs` from `params["arguments"]` with no enforcement against the tool's declared `input_schema`. That code is unchanged prior to version 4.6.40. A single unauthenticated MCP `tools/call` to `praisonai.workflow.show` returns the contents of any file the host user can read: `/etc/passwd`, `~/.ssh/id_rsa`, `~/.aws/credentials`, or any project `.env`. Version 4.6.40 contains an updated fix.

Weakness: CWE-862 (Missing Authorization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

3 open source packages ship an affected version, including praisonai and PraisonAI.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `praisonai` | PyPI | All versions | 4.6.40 |
| `praisonai` | PyPI | All versions | 4.6.40 |
| `PraisonAI` | PyPI | All versions | 4.6.40 |

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

Upgrade praisonai to 4.6.40 or later.

## Is CVE-2026-47394 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47394 is a high-severity path traversal vulnerability in MervinPraison PraisonAI, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47394 exists.

Affected packages and fixed versions:
- praisonai (PyPI): affected all versions; fixed in 4.6.40
- praisonai (PyPI): affected all versions; fixed in 4.6.40
- PraisonAI (PyPI): affected all versions; fixed in 4.6.40

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-47394/ (Markdown: https://insights.sbomify.com/CVE-2026-47394/index.md)
```

## Sources

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

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