CVE-2026-40289
published 2026-04-14CVE-2026-40289: PraisonAI is a multi-agent teams system. In versions below 4.5.139 of PraisonAI and 1.5.140 of praisonaiagents, the browser bridge (praisonai browser start) is…
PriorityP263critical9.1CVSS 3.1
AVNACLPRNUINSUCHIHAN
EPSS
0.52%
41.7th percentile
PraisonAI is a multi-agent teams system. In versions below 4.5.139 of PraisonAI and 1.5.140 of praisonaiagents, the browser bridge (praisonai browser start) is vulnerable to unauthenticated remote session hijacking due to missing authentication and a bypassable origin check on its /ws WebSocket endpoint. The server binds to 0.0.0.0 by default and only validates the Origin header when one is present, meaning any non-browser client that omits the header is accepted without restriction. An unauthenticated network attacker can connect, send a start_session message, and the server will route it to the first idle browser-extension WebSocket (effectively hijacking that session) and then broadcast all resulting automation actions and outputs back to the attacker. This enables unauthorized remote control of connected browser automation sessions, leakage of sensitive page context and automation results, and misuse of model-backed browser actions in any environment where the bridge is network-reachable. This issue has been fixed in versions 4.5.139 of PraisonAI and 1.5.140 of praisonaiagents.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| mervinpraison | praisonai | < 4.6.58 | 4.6.58 |
| mervinpraison | praisonai | >= 0 < 4.6.58 | 4.6.58 |
| mervinpraison | praisonai | >= 0 < 4.5.139 | 4.5.139 |
| mervinpraison | praisonaiagents | >= 0 < 1.5.140 | 1.5.140 |
| praison | praisonai | < 4.5.139 | 4.5.139 |
| praison | praisonaiagents | < 1.5.140 | 1.5.140 |
CVSS provenance
nvdv3.19.1CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
ghsa9.1CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
PraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92)
ghsa·2026-08-25·CVSS 9.1
CVE-2026-55536 [CRITICAL] CWE-284 PraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92)
PraisonAI has a Browser Server WebSocket origin validation bypass via unanchored regex (patch bypass of CVE-2026-40289 / GHSA-8x8f-54wf-vv92)
### Summary
`praisonai/browser/server.py` validates incoming WebSocket connections using a Chrome
extension Origin check. The regex `chrome-extension://[a-z0-9]{32}` is applied with
`re.match()`, which **only anchors at the start of the string, not the end**. Any Origin
header with more than 32 alphanumeric characters after `chrome-extension://` — including
non-alphanumeric trailing characters — passes the check.
This is a **patch bypass** of GHSA-8x8f-54wf-vv92. That advisory triggered the addition
of origin validation; this finding shows the validation is bypassable by any WebSocket
client that forges an Origin header. After bypassing, the attac
GHSA
PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension sessions
ghsa·2026-04-10
CVE-2026-40289 [CRITICAL] CWE-306 PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension sessions
PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension sessions
### Summary
`praisonai browser start` exposes the browser bridge on `0.0.0.0` by default, and its `/ws` endpoint accepts websocket clients that omit the `Origin` header entirely. An unauthenticated network client can connect as a fake controller, send `start_session`, cause the server to forward `start_automation` to another connected browser-extension websocket, and receive the resulting action/status stream back over that hijacked session. This allows unauthorized remote use of a connected browser automation session without any credentials.
### Details
The issue is in the browser bridge trust model. The code assumes that websocket peers are trusted local components, but that assumpt
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-04-14
Published