OpenClaw: ब्राउज़र नियंत्रण स्टार्टअप प्रमाणीकरण बूटस्ट्रैप विफलता के बाद भी अनधिकृत रूप से जारी रह सकता है

An attacker exploiting this vulnerability could gain unauthorized access to browser-control routes within OpenClaw. This access could include the ability to execute evaluate-capable actions, potentially leading to remote code execution or data manipulation depending on the specific actions available through the browser-control interface. The vulnerability is particularly concerning because it can be exploited via a local process or through an SSRF (Server-Side Request Forgery) path, meaning an attacker doesn't necessarily need to be on the same network as the OpenClaw instance. Successful exploitation could allow an attacker to control the browser and potentially compromise the underlying system.

Organizations deploying OpenClaw in environments with potential SSRF vulnerabilities are at the highest risk. This includes deployments where the OpenClaw instance has access to internal services or resources that could be leveraged for SSRF attacks. Shared hosting environments where multiple users share the same OpenClaw instance are also at increased risk.

• nodejs / server:

  ps aux | grep openclaw

• nodejs / server:

  npm list -g openclaw

• nodejs / server:

  journalctl -u openclaw --since "1 hour ago"

• generic web:

  curl -I http://<openclaw_host>/browser-control/evaluate

• generic web:

  grep -r "browser-control/evaluate" /var/log/nginx/access.log

1. 2026-03-02Disclosure

   disclosure

1. आरक्षित2026-03-10
2. प्रकाशित2026-03-02
3. संशोधित2026-03-30
4. EPSS अद्यतन2026-03-27

The primary mitigation for CVE-2026-32041 is to upgrade OpenClaw to version 2026.3.1 or later. This version implements a fix that prevents startup if authentication bootstrapping fails, effectively closing off the unauthenticated access path. If upgrading is not immediately feasible, consider implementing strict network segmentation to limit SSRF access to the OpenClaw instance. Additionally, ensure that any existing authentication mechanisms are robust and properly configured. There are no specific WAF rules or detection signatures readily available, so focus on patching and network isolation.