CVE-2026-39308 Details
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.
A path traversal vulnerability allowing arbitrary file writes has been identified in PraisonAI versions prior to 1.5.113. The issue arises in the recipe registry publish endpoint, which writes uploaded recipe bundles to a filesystem path based on the bundle's internal manifest.json. This occurs before the endpoint verifies that the manifest's name and version match the HTTP route. As a result, a malicious publisher can inject traversal sequences into the manifest, causing the server to create files outside the designated registry root. Although the request is ultimately rejected with an HTTP 400 response, the unauthorized file write has already taken place. This vulnerability affects deployments that expose the recipe registry publish functionality. If the registry is run without a token, any network client can exploit the issue. Even with a token, users with publish access can trigger the vulnerability.
Users are advised to validate the 'manifest.json' name and version before any filesystem write, rejecting path separators, traversal sequences, absolute paths, and any values that do not pass the existing validation checks. Additionally, the final destination path should be resolved and checked to ensure it remains within the registry root before writing files.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 9, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-r9x3-wx45-2v7f | CISA-ADP | ExploitMitigationVendor Advisory |
| https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-r9x3-wx45-2v7f | [email protected] | ExploitMitigationVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| praison praisonai | <= 4.5.112 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 16, 2026 | Initial Analysis | [email protected] |
| Apr 9, 2026 | CVE Modified | CISA-ADP |
| Apr 7, 2026 | New CVE Received | [email protected] |