Vulnerability in PraisonAI (CVE-2026-55532)
Summary
Vulnerability in PraisonAI (CVE-2026-55532). Data can be tampered with by attackers. Exploitable via Host header. Mitigation: upgrade to 4.6.58 or later.
Original description
The description as published by the source.
Summary
The PraisonAI MCP server exposes an HTTP-stream transport (praisonai mcp serve --transport http-stream) that binds to localhost and, by default, has no API key. Its only access control for browser-originated requests is an Origin allowlist, which the code implements as required by the MCP 2025-11-25 security guidance. The allowlist check uses a prefix match (request_origin.startswith(allowed)), so any Origin whose string begins with http://localhost or http://127.0.0.1 is accepted, for example http://localhost.attacker.com. An attacker who registers such a hostname and serves a page from it can, when a victim visits the page, issue cross-site requests that the MCP server accepts and executes without authentication. Because the request can be sent as a CORS "simple request" (Content-Type: text/plain, which the server still parses as JSON), it requires no preflight, and because tools/call does not require a session, a single forged request executes an MCP tool. This is a blind cross-site request forgery against a developer's local agent runtime. A natural end-to-end impact is persistent prompt injection: the forged request creates a rule file that the agent runtime loads with activation "always", so attacker-controlled instructions are injected into every subsequent agent run on the victim's machine.
Details
The HTTP-stream transport validates the Origin header in transports/http_stream.py. The allowlist is built for a localhost bind, then matched with starts…
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-55532 has been found in PraisonAI.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.6/10.
What to do: upgrade PraisonAI to 4.6.58 or later.
If unsure, ask your IT team or search "PraisonAI CVE-2026-55532" on the vendor's site.
CVE-2026-55532 (PraisonAI) — CWE-346 / CVSS v3 7.6
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Host header
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-346) exists in PraisonAI. Attackers reach the vulnerable code path via Host header without authentication.
Check the vendor advisory for the affected versions of PraisonAI. Attack surface: Host header.
Severity: High (CVSS 7.6/10). Data can be tampered with by attackers.
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 でアラート再発が無いか継続監視。