Path Traversal in praisonai (CVE-2026-39308)

Summary

Path traversal in praisonai (CVE-2026-39308). Data can be tampered with by attackers. Exploitable via POST /v1/recipes/{name}/{version}. Mitigation: upgrade to 4.5.113 or later.

Original description

The description as published by the source.

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.

RegistryServer._handle_publish() in src/praisonai/praisonai/recipe/server.py:370-426 parses POST /v1/recipes/{name}/{version}, writes the uploaded .praison file to a temporary path, and immediately calls:

result = self.registry.publish(tmp_path, force=force)

LocalRegistry.publish() in src/praisonai/praisonai/recipe/registry.py:214-287 opens the uploaded tarball, reads manifest.json, and trusts the attacker-controlled name and version fields:

name = manifest.get("name")
version = manifest.get("version")
recipe_dir = se…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-39308 has been found in praisonai.
Attackers can target a specific entry point like POST /v1/recipes/{name}/{version} over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade praisonai to 4.5.113 or later.
If unsure, ask your IT team or search "praisonai CVE-2026-39308" on the vendor's site.

CVE-2026-39308 (praisonai) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /v1/recipes/{name}/{version} / name / version
Patched: 4.5.113 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in praisonai. Attackers reach the vulnerable code path via POST /v1/recipes/{name}/{version}.

📍 Affected scope

Check the vendor advisory for the affected versions of praisonai. Attack surface: POST /v1/recipes/{name}/{version} / name / version.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 4.5.113.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /v1/recipes/{name}/{version} requests with malformed payloads or SQL meta-characters. Run grep -r 'praisonai' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'praisonai' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で praisonai を grep し、稼働しているサービス・バージョンを把握する。
2
Hunt for indicators of compromise detect
```
grep 'POST /v1/recipes/{name}/{version}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'
```
アクセスログで POST /v1/recipes/{name}/{version} への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
3
Apply patch patch
```
Upgrade praisonai to 4.5.113
```
ステージング環境で 4.5.113 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
4
Post-deployment verification verify
```
Replay attack against POST /v1/recipes/{name}/{version} on staging to confirm patch closes the vector
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI praisonai

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.113"}]}]

References

advisory nvd.nist.gov
package github.com
web github.com
web github.com