← Back
CVE-2026-56074
medium
CVSS 5.5
Authorization Flaw in praisonai (CVE-2026-56074)
Summary
vulnerability in praisonai (CVE-2026-56074). Confidential information can be exposed externally. Exploitable via ``execute_command``. Mitigation: upgrade to `4.5.128` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-56074** has been found in praisonai.
Attackers can target a specific entry point like ``execute_command`` 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.5.128** or later.
If unsure, ask your IT team or search "praisonai CVE-2026-56074" on the vendor's site.
CVE-2026-56074 (praisonai) — CWE-863 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: `execute_command` / `require_approval` / `mark_approved` / `ConsoleBackend`
Patched: `4.5.128` — 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
**incorrect authorization** (CWE-863) exists in praisonai. Attackers reach the vulnerable code path via ``execute_command`` without authentication.
📍 Affected scope
praisonai — . Attack surface: `execute_command` / `require_approval` / `mark_approved` / `ConsoleBackend`.
🔥 Severity
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **4.5.128**.
🛡️ 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 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade praisonai to 4.5.128ステージング環境で 4.5.128 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
praisonai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
pip
praisonaiagents
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.5.128"}]}]