Vulnerability in PraisonAI (CVE-2026-55529)
Summary
Vulnerability in PraisonAI (CVE-2026-55529). Confidential information can be exposed externally. Exploitable via Origin. Mitigation: upgrade to 4.6.58 or later.
Original description
The description as published by the source.
Summary
PraisonAI's MCP HTTP Stream transport uses an unsafe prefix match when validating the Origin header. The default localhost allowlist includes origins such as http://localhost, and the validation accepts any origin that starts with an allowed value.
As a result, an attacker-controlled origin such as http://localhost.evil.example passes the localhost origin check.
When the MCP HTTP Stream server is started without an API key, which is the CLI default, this allows a malicious webpage to trigger unauthenticated MCP tools/call requests against a locally running PraisonAI MCP server.
This is best framed as a browser-mediated localhost attack / DNS-rebinding-style Origin validation bypass. The default server binds to 127.0.0.1, so this is not a directly internet-facing unauthenticated API in the default configuration.
Details
Relevant source locations:
src/praisonai/praisonai/mcp_server/cli.pysrc/praisonai/praisonai/mcp_server/transports/http_stream.pysrc/praisonai/praisonai/mcp_server/server.pysrc/praisonai/praisonai/mcp_server/adapters/__init__.pysrc/praisonai/praisonai/mcp_server/adapters/extended_capabilities.pysrc/praisonai/praisonai/mcp_server/adapters/cli_tools.pysrc/praisonai/praisonai/capabilities/files.py
The MCP CLI defaults to HTTP host 127.0.0.1, API key None, and allowed origins None unless explicitly configured:
parser.add_argument("--host", default="127.0.0.1")
parser.add_argument("-…
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-55529 has been found in PraisonAI.
Attackers can target a specific entry point like Origin over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.9/10.
What to do: upgrade PraisonAI to 4.6.58 or later.
If unsure, ask your IT team or search "PraisonAI CVE-2026-55529" on the vendor's site.
CVE-2026-55529 (PraisonAI) — CWE-306 / CVSS v3 6.9
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Origin / None / allowed_origins / praisonai.files.create
Patched: 4.6.58 — 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.
A vulnerability (CWE-306) exists in PraisonAI. Attackers reach the vulnerable code path via Origin without authentication.
Check the vendor advisory for the affected versions of PraisonAI. Attack surface: Origin / None / allowed_origins / praisonai.files.create.
Severity: Medium (CVSS 6.9/10). Confidential information can be exposed externally.
Update to 4.6.58.
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.58ステージング環境で 4.6.58 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。