PraisonAI: Origin-validation bypass (startswith prefix match) enables unauthenticated cross-site request forgery against the PraisonAI MCP H
CVE-2026-55532 · GHSA-pvph-5j39-v8qc · published 2026-08-25
- Severity
- High
- CVSS score
- 7.6
- Chance of exploitation (EPSS)
- 0.20%
- Fixed in
- 4.6.58
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
A developer running the PraisonAI MCP server locally with the default HTTP-stream transport and no API key can be attacked by any web page they visit. The page forges an unauthenticated cross-site request to 127.0.0.1, which passes the Origin allowlist because of the startswith prefix match. The attacker can invoke state-changing MCP tools blind. The most serious demonstrated consequence is persistent prompt injection: the forged request writes a rule that the agent runtime loads with activation "always", so the attacker plants instructions (for example, exfiltrate SSH keys and API keys) that are silently applied to every later agent run, escalating to confidentiality loss on the next invoca…
Upgrade praisonai to 4.6.58 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Replace the prefix match with an exact, parsed-origin comparison: compare the scheme, host, and port of the request Origin against the allowlist (urllib.parse), never startswith. Treat a missing Origin conservatively for state-changing methods rather than allowing it unconditionally, and validate the Host header to defend against DNS rebinding. Strongly consider requiring authentication by default for the HTTP-stream transport (generate and print a token when none is supplied), and reject request bodies whose Content-Type is not application/json so that browser "simple requests" cannot reach the JSON-RPC dispatcher without a preflight.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonai | PyPI | < 4.6.58 | 4.6.58 |
1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.
- io.github.MervinPraison/praisonaipraisonai@2.3.42
- CriticalMarimo: Pre-Auth Remote Code Execution via Terminal WebSocket Authentication BypassmarimoExploited
- CriticalLangflow CORS misconfiguration enables Account Takeover and RCElangflowExploited
- HighLiteLLM: MCP Authentication Bypass via OAuth2 Passthrough FallbacklitellmExploited
- HighLangflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowlangflowExploited
- CriticalTodoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server@doist/todoist-mcp
- CriticalLangflow: Unauthenticated Flow Execution via Webhook Authentication Bypasslangflow
- CriticalPraisonAI: AICoder Arbitrary File Write and Command Execution via LLM Tool Callspraisonai
- CriticalPraisonAI: Code Injection via f-string Interpolation in Deploy API Server Generationpraisonai
- CriticalPraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92praisonai
- CriticalPraisonAI: Arbitrary File Read/Write via `multiedit` Tool Without Path Validationpraisonai
- CriticalPraisonAI: Unauthenticated RCE via Jobs API + Approval Bypasspraisonaiagents, praisonai
- CriticalPraisonAI: AgentOS remains unauthenticated after incomplete fix version and allows remote agent invocationpraisonai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.