PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI's recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected. This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself. This vulnerability is fixed in 1.5.113.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534 Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.3 · praisonNVD modified 2026-10-26 21:10
Affected (CPE criteria) 1
cpe:2.3:a:praison:praisonai:*:*:*:*:*:*:*:*
References 1
- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4rx4-4r3x-6534 Exploit, Vendor Advisory