PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension sessions
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in PraisonAI 4.5.139, praisonai 4.5.139 and praisonaiagents 1.5.140.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| MervinPraison | <1.5.140, <4.5.139 | ||
| pypi: PraisonAI | <=4.5.138 | 4.5.139 | |
| pypi: praisonai | <4.5.139 | 4.5.139 | |
| pypi: praisonaiagents | <1.5.140, <=1.5.139 | 1.5.140 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in praisonai (PyPI), strongest first
Embed
A live severity badge for an advisory, README or ticket