Path Traversal in praisonai (CVE-2026-60088)
Summary
Path traversal in praisonai (CVE-2026-60088). Confidential information can be exposed externally. Exploitable via PYTHONPATH. Mitigation: upgrade to 4.6.78 or later.
Original description
The description as published by the source.
PraisonAI before 4.6.78 fails to validate file path references in custom command templates, allowing attackers to read files outside the workspace. Attackers can include path traversal sequences like @../outside_secret.txt or absolute paths in project command files to exfiltrate process-readable files into model prompts.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-60088 has been found in praisonai.
Attackers can target a specific entry point like PYTHONPATH over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade praisonai to 4.6.78 or later.
If unsure, ask your IT team or search "praisonai CVE-2026-60088" on the vendor's site.
CVE-2026-60088 (praisonai) — CWE-22 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: PYTHONPATH / praisonai / praisonai.cli.features.custom_definitions / custom_definitions.py
Patched: 4.6.78 — 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 PYTHONPATH without authentication.
Check the vendor advisory for the affected versions of praisonai. Attack surface: PYTHONPATH / praisonai / praisonai.cli.features.custom_definitions / custom_definitions.py.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 4.6.78.
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.6.78ステージング環境で 4.6.78 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- web github.com