Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-47398 high CVSS 8.1

Vulnerability in PraisonAI (CVE-2026-47398)

Summary

Vulnerability in PraisonAI (CVE-2026-47398). Successful exploitation can lead to full system takeover. Exploitable via POST /v1/recipes/run. Mitigation: upgrade to 4.6.40 or later.

Original description

The description as published by the source.

Arbitrary code execution via ungated spec.loader.exec_module in agents_generator.py (v4.6.32 chokepoint refactor bypass)
Summary
The v4.6.32 chokepoint refactor (which patched CVE-2026-44334 / GHSA-xcmw-grxf-wjhj) added the PRAISONAI_ALLOW_LOCAL_TOOLS env-var gate to the tool_override.py sinks. However, two additional spec.loader.exec_module call sites in praisonai/agents_generator.py were missed and remain completely unguarded on current master (v4.6.37). Both functions accept a module_path parameter sourced from YAML configuration and execute it without validation, signature checking, or the env-var gate.
Patch lineage

CVE GHSA Fixed in What was patched
CVE-2026-40156 GHSA-2g3w-cpc4-chr4 4.5.128 CWD tools.py auto-load in tool_resolver.py
CVE-2026-40287 GHSA-g985-wjh9-qxxc 4.5.139 Env-var gate added to tool_resolver.py + api/call.py
CVE-2026-44334 GHSA-xcmw-grxf-wjhj 4.6.32 Missed sink in templates/tool_override.py
This finding — unfixed Missed sinks in agents_generator.py

Every prior patch addressed a subset of exec_module call sites. The two sinks documented here were present throughout the entire fix sequence and remain unpatched.
Vulnerable code

praisonai/agents_generator.py (master HEAD; v4.6.37)

336 def load_tools_from_module(self, module_path):
# ...
349 spec = importlib.util.spec_from_file_location("tools_module", module_path)
350 module = importlib.util.module_from_spec(spec)
351…

Source: GitHub Security Advisories (Global) 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-47398 has been found in PraisonAI.
Attackers can target a specific entry point like POST /v1/recipes/run over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade PraisonAI to 4.6.40 or later.
If unsure, ask your IT team or search "PraisonAI CVE-2026-47398" on the vendor's site.

CVE-2026-47398 (PraisonAI) — CWE-829 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /v1/recipes/run / spec.loader.exec_module / agents_generator.py / PRAISONAI_ALLOW_LOCAL_TOOLS
Patched: 4.6.40 — 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

A vulnerability (CWE-829) exists in PraisonAI. Attackers reach the vulnerable code path via POST /v1/recipes/run without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of PraisonAI. Attack surface: POST /v1/recipes/run / spec.loader.exec_module / agents_generator.py / PRAISONAI_ALLOW_LOCAL_TOOLS.

🔥 Severity

Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.6.40.

🛡️ 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/run 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. 1
    Identify exposure identify 
    grep -r 'PraisonAI' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で PraisonAI を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /v1/recipes/run' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /v1/recipes/run への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade PraisonAI to 4.6.40

    ステージング環境で 4.6.40 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /v1/recipes/run on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

pip PraisonAI
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.6.40"}]}]
PyPI praisonai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.6.40"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details