CVE-2026-39308

PraisonAI recipe registry publish path traversal allows out-of-root file write

This is a path traversal / arbitrary file write vulnerability in the recipe registry publish flow.

Impacted parties:

• Registry operators running the PraisonAI recipe registry service.
• Any deployment that allows remote recipe publication.
• Any environment where adjacent writable filesystem locations contain sensitive application data, service files, or staged content that could be overwritten or planted.

Security impact:

• Integrity impact is high because an attacker can create or overwrite files outside the registry root.
• Availability impact is possible if the attacker targets adjacent runtime or application files.
• The issue can be chained with other local loading or deployment behaviors if nearby files are later consumed by another component.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-39308 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.5.113); upgrading removes the vulnerable code path.

Kodem intelligence

1. Validate manifest.json name and version before any path join or filesystem write. Reject path separators, .., absolute paths, and any value that fails the existing _validate_name() / _validate_version() checks.

2. Resolve the final destination path and enforce that it remains under the configured registry root before calling mkdir() or copy2(). For example, compare the resolved destination against self.recipes_path.resolve().

3. Move the URL-to-manifest consistency check ahead of self.registry.publish(...), or refactor publish() so it receives already-validated route parameters instead of trusting attacker-controlled manifest values for storage paths.

1. What is CVE-2026-39308? CVE-2026-39308 is a high-severity path traversal vulnerability in PraisonAI (pip), affecting versions <= 4.5.112. It is fixed in 4.5.113. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-39308? CVE-2026-39308 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of PraisonAI are affected by CVE-2026-39308? PraisonAI (pip) versions <= 4.5.112 is affected.
4. Is there a fix for CVE-2026-39308? Yes. CVE-2026-39308 is fixed in 4.5.113. Upgrade to this version or later.
5. Is CVE-2026-39308 exploitable, and should I be worried? Whether CVE-2026-39308 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-39308 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-39308? Upgrade PraisonAI to 4.5.113 or later.