UTC
Critical

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
What it is

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

What to do

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.

Affected
PackageRegistryAffectedFixed in
praisonaiagentsPyPI<= 1.5.1391.5.140
praisonaiPyPI<= 4.5.1384.5.139
Downstream in the Official MCP Registry

1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.

  • io.github.MervinPraison/praisonaipraisonai@2.3.42
See the trace →

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.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].