PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension sessions
CVE-2026-40289 · GHSA-8x8f-54wf-vv92 · published 2026-04-10 · updated 2026-11-16
- Severity
- Critical
- CVSS score
- 9.1
- Chance of exploitation (EPSS)
- 0.43%
- Fixed in
- 1.5.140
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
This is an unauthenticated remote-control vulnerability in the browser automation bridge. Any network client that can reach the exposed bridge can impersonate the controller side of the workflow, hijack an available connected extension session, and receive automation output from that hijacked session. In real deployments, this can allow unauthorized browser actions, misuse of model-backed automation, and leakage of sensitive page context or automation results. Who is impacted: Operators who run praisonai browser start with the default host binding Users with an active connected browser extension session Environments where the bridge is reachable from other hosts on the network
Upgrade praisonaiagents to 1.5.140 or later, and praisonai to 4.5.139 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.
Suggested remediations: 1. Require explicit authentication for every websocket client connecting to /ws. 2. Reject websocket handshakes that omit Origin, unless they are using a separate authenticated localhost-only transport. 3. Bind the browser bridge to 127.0.0.1 by default and require explicit operator opt-in for non-loopback exposure. 4. Do not route start_session to “the first other idle connection”; instead, pair authenticated controller and extension clients explicitly.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| praisonaiagents | PyPI | <= 1.5.139 | 1.5.140 |
| praisonai | PyPI | <= 4.5.138 | 4.5.139 |
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: CodeAgent Executes LLM-Generated Code Without Sandboxing and Leaks All Environment Secretspraisonaiagents
- 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
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.