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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

EPSS

• CVE-2026-39308: 0.33% estimated exploitation activity in the next 30 days; percentile 26.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details The bug is caused by the order of operations between the HTTP handler and the registry storage layer. 1. RegistryServer.handlepublish() in src/praisonai/praisonai/recipe/server.py:370-426 parses…

Published by the source

6 Apr 2026, 23:09 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-r9x3-wx45-2v7f

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-r9x3-wx45-2v7f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-39308

Advisory: PraisonAI recipe registry publish path traversal allows out-of-root file write
IDs: CVE-2026-39308, GHSA-r9x3-wx45-2v7f
Record: https://patchnext.com/advisories/cve-2026-39308 (revision 2, source checked 26 Oct 2026, 13:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai 4.5.113. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected <= 4.5.112; fixed in 4.5.113

## Suggested inspection (read-only)
- `python -m pip show praisonai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-r9x3-wx45-2v7f (OSV record GHSA-r9x3-wx45-2v7f lists affected ranges: PyPI praisonai >=0 <4.5.113 (fixed))
- Verified: https://github.com/advisories/GHSA-r9x3-wx45-2v7f (GitHub-reviewed advisory GHSA-r9x3-wx45-2v7f lists affected ranges: PyPI praisonai >=0 <=4.5.112)

Commands are suggestions: review each one before running it.