Vulnerability Description
PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI's recipe registry publish endpoint writes uploaded recipe bundles to a filesystem path derived from the bundle's internal manifest.json before it verifies that the manifest name and version match the HTTP route. A malicious publisher can place ../ traversal sequences in the bundle manifest and cause the registry server to create files outside the configured registry root even though the request is ultimately rejected with HTTP 400. This is an arbitrary file write / path traversal issue on the registry host. It affects deployments that expose the recipe registry publish flow. If the registry is intentionally run without a token, any network client that can reach the service can trigger it. If a token is configured, any user with publish access can still exploit it. This vulnerability is fixed in 1.5.113.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Praison | Praisonai | <= 4.5.112 |
Related Weaknesses (CWE)
References
- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-r9x3-wx45-2vExploitMitigationVendor Advisory
- https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-r9x3-wx45-2vExploitMitigationVendor Advisory
FAQ
What is CVE-2026-39308?
CVE-2026-39308 is a vulnerability with a CVSS score of 7.1 (HIGH). PraisonAI is a multi-agent teams system. Prior to 1.5.113, PraisonAI's recipe registry publish endpoint writes uploaded recipe bundles to a filesystem path derived from the bundle's internal manifest....
How severe is CVE-2026-39308?
CVE-2026-39308 has been rated HIGH with a CVSS base score of 7.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-39308?
Check the references section above for vendor advisories and patch information. Affected products include: Praison Praisonai.