Path Traversal in praisonai (CVE-2026-39306)
Summary
Path traversal in praisonai (CVE-2026-39306). Data can be tampered with by attackers. Exploitable via recipe_dir. Mitigation: upgrade to 4.5.113 or later.
Original description
The description as published by the source.
Summary
PraisonAI's recipe registry pull flow extracts attacker-controlled .praison tar archives with tar.extractall() and does not validate archive member paths before extraction. A malicious publisher can upload a recipe bundle that contains ../ traversal entries and any user who later pulls that recipe will write files outside the output directory they selected.
This is a path traversal / arbitrary file write vulnerability on the client side of the recipe registry workflow. It affects both the local registry pull path and the HTTP registry pull path. The checksum verification does not prevent exploitation because the malicious traversal payload is part of the signed bundle itself.
Details
The issue is caused by unsafe extraction of tar archive contents during recipe pull.
- A malicious publisher creates a valid
.praisonbundle whosemanifest.jsonis benign enough to pass publish, but whose tar members include traversal entries such as:
../../escape-http.txt
-
LocalRegistry.publish()insrc/praisonai/praisonai/recipe/registry.py:214-287only readsmanifest.json, calculates a checksum, and stores the uploaded bundle. It does not inspect or sanitize the rest of the tar members before saving the archive. -
When a victim later pulls the recipe from a local registry,
LocalRegistry.pull()insrc/praisonai/praisonai/recipe/registry.py:289-345extracts the tarball directly:
recipe_dir = output_dir / name
recipe_dir.mkdir…
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-39306 has been found in praisonai.
Attackers can target a specific entry point like recipe_dir 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-39306" on the vendor's site.
CVE-2026-39306 (praisonai) — CWE-22
Attack vector: remote (network-reachable)
Attack surface: recipe_dir / TarInfo
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.
Path traversal (CWE-22) exists in praisonai. Attackers reach the vulnerable code path via recipe_dir.
Check the vendor advisory for the affected versions of praisonai. Attack surface: recipe_dir / TarInfo.
Severity: ?. Data can be tampered with by attackers.
Update to 4.5.113.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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
-
1Identify exposure identify
grep -r 'praisonai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
praisonaiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade praisonai to 4.5.113ステージング環境で 4.5.113 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com