Path Traversal in praisonai (CVE-2026-61445)
Summary
Path traversal in praisonai (CVE-2026-61445). Successful exploitation can lead to full system takeover. Exploitable via AICoder. Mitigation: upgrade to 4.6.78 or later.
Original description
The description as published by the source.
PraisonAI before 4.6.78 contains arbitrary file write and command execution vulnerabilities in the AICoder component due to missing path validation and command sanitization in LLM tool calls. Attackers can inject malicious prompts through the chat interface to write files to arbitrary filesystem locations and execute arbitrary shell commands with root privileges.
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-61445 has been found in praisonai.
Attackers can target a specific entry point like AICoder over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade praisonai to 4.6.78 or later.
If unsure, ask your IT team or search "praisonai CVE-2026-61445" on the vendor's site.
CVE-2026-61445 (praisonai) — CWE-22 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: AICoder / write_to_file / execute_command / apply_llm_response
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 AICoder.
Check the vendor advisory for the affected versions of praisonai. Attack surface: AICoder / write_to_file / execute_command / apply_llm_response.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
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
- web github.com