Information Disclosure in PraisonAI (CVE-2026-47394)
Summary
Vulnerability in PraisonAI (CVE-2026-47394). Risk of unauthorized operations or information disclosure. Exploitable via praisonai.rules.create. Mitigation: upgrade to 4.6.40 or later.
Original description
The description as published by the source.
PraisonAI is a multi-agent teams system. Prior to version 4.6.40, the fix for GHSA-9mqq-jqxf-grvw / CVE-2026-44336 is incomplete. The original advisory description named four vulnerable handlers in mcp_server/adapters/cli_tools.py. Commit 68cc9427 ("fix(security): harden MCP rules path handling…") added a _resolve_rule_path() helper and applied it to rules.create, rules.show, and rules.delete. workflow.show was left unchanged. Two adjacent handlers in the same file have the same pattern, workflow.validate and deploy.validate. Neither was mentioned in the original advisory. Both remained unchanged. The original advisory also identified the dispatcher (server.py:281-298) as a root cause. It accepts unvalidated **kwargs from params["arguments"] with no enforcement against the tool's declared input_schema. That code is unchanged prior to version 4.6.40. A single unauthenticated MCP tools/call to praisonai.workflow.show returns the contents of any file the host user can read: /etc/passwd, ~/.ssh/id_rsa, ~/.aws/credentials, or any project .env. Version 4.6.40 contains an updated fix.
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-47394 has been found in PraisonAI.
Attackers can target a specific entry point like praisonai.rules.create over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade PraisonAI to 4.6.40 or later.
If unsure, ask your IT team or search "PraisonAI CVE-2026-47394" on the vendor's site.
CVE-2026-47394 (PraisonAI) — CWE-200
Attack surface: praisonai.rules.create / praisonai.rules.show / praisonai.rules.delete / praisonai.workflow.show
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.
Information disclosure (CWE-200) exists in PraisonAI. Attackers reach the vulnerable code path via praisonai.rules.create.
Check the vendor advisory for the affected versions of PraisonAI. Attack surface: praisonai.rules.create / praisonai.rules.show / praisonai.rules.delete / praisonai.workflow.show.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 4.6.40.
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.40ステージング環境で 4.6.40 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com